From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-developers@cygwin.com
Subject: Re: Evil deed: Switching development repository to git
Date: Tue, 10 Mar 2015 15:59:00 -0000 [thread overview]
Message-ID: <54FF14F3.3090702@dronecode.org.uk> (raw)
In-Reply-To: <20150305151250.GA8041@calimero.vinschen.de>
On 05/03/2015 15:12, Corinna Vinschen wrote:
> next week, I'm planning to move the combined newlib/libgloss and cygwin
> repository from CVS to git. The basic stuff is quickly done, but hooks,
> mailing list handling, and changes to the websites are to be done, so I
> expect the switch to take about two days.
>
> I'll set up a commit moratorium starting next Monday at about 10:00 UTC.
>
> When the git repo is up and working I'll throw the lever and inform the
> mailing lists. Afterwards you can expect to access the new combined
> newlib/cygwin git repository via either
>
> git clone git://sourceware.org/git/newlib-cygwin.git
>
> or, if you have write permissions on the repo
>
> git clone sourceware.org:/git/newlib-cygwin.git
Many thanks for this!
If you have write permissions, you may find it more convenient to do:
git clone git://sourceware.org/git/newlib-cygwin.git
git remote set-url --push origin sourceware.org:/git/newlib-cygwin.git
... as then you don't have to authenticate to pull, only to push.
next prev parent reply other threads:[~2015-03-10 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 15:12 Corinna Vinschen
2015-03-10 15:59 ` Jon TURNEY [this message]
2015-03-10 19:45 ` Corinna Vinschen
[not found] <20150305145541.GA20560@calimero.vinschen.de>
[not found] ` <F2C22140-82E0-470B-9F87-9DC45503CA9C@oarcorp.com>
2015-03-05 15:59 ` Corinna Vinschen
[not found] ` <alpine.DEB.2.10.1503062257590.9654@digraph.polyomino.org.uk>
2015-03-09 10:53 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54FF14F3.3090702@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-developers@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).