From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org, cygwin-developers@cygwin.com
Subject: Re: Evil deed: Switching development repository to git
Date: Mon, 09 Mar 2015 10:53:00 -0000 [thread overview]
Message-ID: <20150309105258.GA30834@calimero.vinschen.de> (raw)
In-Reply-To: <alpine.DEB.2.10.1503062257590.9654@digraph.polyomino.org.uk>
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
On Mar 6 23:02, Joseph Myers wrote:
> On Thu, 5 Mar 2015, Corinna Vinschen wrote:
>
> > Hi folks,
> >
> >
> > 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.
>
> Exactly which files and directories from the src repository will be
> included in the new git repository?
>
> Will the src CVS repository be made read-only after the move (the whole
> thing rather than just the moved directories)?
I'm not the one to make such a decision. I'm moving newlib and cygwin
to git and disallow further checkins into these two project subdirs
inside the CVS tree, nothing else.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-09 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2015-03-05 15:12 Corinna Vinschen
2015-03-10 15:59 ` Jon TURNEY
2015-03-10 19:45 ` 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=20150309105258.GA30834@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=cygwin-developers@cygwin.com \
--cc=newlib@sourceware.org \
/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).