From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Jeff Johnston <jjohnstn@redhat.com>
Cc: <overseers@sourceware.org>
Subject: Re: sourceware and git
Date: Tue, 29 Jul 2014 18:14:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1407291812320.19626@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1942527352.18336706.1406653023761.JavaMail.zimbra@redhat.com>
On Tue, 29 Jul 2014, Jeff Johnston wrote:
> There have been some requests to put newlib into git. I was wondering if
> the overseers have recently looked into putting sourceware into git.
>
> I am also wondering how a piece of sourceware can be put into git
> without disrupting it. What steps were needed to move binutils and gdb
> over? Apparently, the gdb-cvs mailing list continues to work and I
> would like to have the same occur for our newlib-cvs list. Any insight
> to the process would be appreciated including issues found.
The basic rule for moving pieces of src CVS is that you move just a
logical project rather than a group of unrelated projects. I.e., if you
want to move newlib to git, just move newlib (the directories and toplevel
files that are used in a newlib build) rather than the whole repository.
Then src CVS can be made readonly as I don't think any of the other
projects have any significant activity.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2014-07-29 18:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <239280260.18333755.1406652387203.JavaMail.zimbra@redhat.com>
2014-07-29 16:57 ` Jeff Johnston
2014-07-29 18:14 ` Joseph S. Myers [this message]
2014-07-30 1:13 ` Christopher Faylor
2014-07-30 7:48 ` Corinna Vinschen
2014-07-30 15:18 ` Christopher Faylor
2014-07-30 15:39 ` Corinna Vinschen
2014-07-30 17:06 ` Joseph S. Myers
2014-07-30 17:27 ` Hans-Peter Nilsson
2014-07-30 17:02 ` Joseph S. Myers
2014-07-30 18:45 ` Christopher Faylor
2014-07-30 20:57 ` Joseph S. Myers
2014-07-30 21:33 ` Christopher Faylor
2014-07-30 21:47 ` Joseph S. Myers
2014-07-30 23:41 ` Yaakov Selkowitz
2014-07-31 2:22 ` Christopher Faylor
2014-08-01 11:05 ` Corinna Vinschen
2014-08-01 22:54 ` Frank Ch. Eigler
2014-08-02 0:12 ` Yaakov Selkowitz
2014-07-29 18:28 ` Tom Tromey
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=Pine.LNX.4.64.1407291812320.19626@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=jjohnstn@redhat.com \
--cc=overseers@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).