From: Tom Tromey <tromey@redhat.com>
To: Jeff Johnston <jjohnstn@redhat.com>
Cc: overseers@sourceware.org
Subject: Re: sourceware and git
Date: Tue, 29 Jul 2014 18:28:00 -0000 [thread overview]
Message-ID: <87lhrcaukt.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1942527352.18336706.1406653023761.JavaMail.zimbra@redhat.com> (Jeff Johnston's message of "Tue, 29 Jul 2014 12:57:03 -0400 (EDT)")
Jeff> What steps were needed to move binutils and gdb over?
The binutils-gdb move was very complicated, primarily because there were
multiple repositories to stitch together, but relatedly because the
original imports to sourceware were done inconsistently.
The steps I followed are documented in the README.md here (just scroll
down):
https://github.com/tromey/gdb-git-migration
All the scripts are there. If you want to reuse them, just fork the
project and hack them up to do what you like.
Jeff> Apparently, the gdb-cvs mailing list continues to work and I would
Jeff> like to have the same occur for our newlib-cvs list.
The mail hook stuff is already on sourceware but you can follow copies
in the "finalize-git-repo" script to see how it is configured.
"src-email" shows how this is done, though your setup may be simpler if
you just have a single commits list.
Tom
prev parent reply other threads:[~2014-07-29 18:28 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
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 [this message]
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=87lhrcaukt.fsf@fleche.redhat.com \
--to=tromey@redhat.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).