From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Jim Meyering <jim@meyering.net>
Cc: gdb@sourceware.org
Subject: Re: gdb.git: author username-to-Full_Name+email map: RFC
Date: Fri, 25 Jul 2008 03:28:00 -0000 [thread overview]
Message-ID: <1216936138.5922.62.camel@localhost.localdomain> (raw)
In-Reply-To: <87abg7s2ce.fsf@rho.meyering.net>
On Thu, 2008-07-24 at 17:56 +0200, Jim Meyering wrote:
> I'm preparing a read-only git mirror of gdb's CVS repository.
> It will be automatically sync'd every ~30 minutes, just as the other
> http://sourceware.org/git/gitweb.cgi mirrors are: glibc, lvm2, dm,
> automake[*]. This gdb.git mirror covers all branches and includes
> all history.
This is awesome. I look forward to use this mirror.
I also like the fact that git log show history for the binutils side
which affects GDB as well.
> It's important to get it right early,
> because redoing the mapping requires changing nearly every SHA1 in the
> resulting git repository, and that is very disruptive.
Do you know if there will be disruption if GDB moves to Subversion?
> If any of you would like to rely on this, please ensure that all
> of the files you care about are in the git repository. For example,
> I heard that three tcl-related directories need not be included, so I
> excluded those along with the likes of ld, gold, gas, etc.
I just compiled from this repo in ppc-linux and ppc64-linux and I saw no
smoke, so it seems sane there.
Thanks for doing this.
--
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center
next prev parent reply other threads:[~2008-07-24 21:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 17:50 Jim Meyering
[not found] ` <je1w1jgslp.fsf@sykes.suse.de>
2008-07-24 20:39 ` Jim Meyering
2008-07-25 3:28 ` Thiago Jung Bauermann [this message]
2008-07-25 13:41 ` Jim Meyering
2008-07-28 10:49 ` Jim Meyering
2008-07-28 11:36 ` Andrew STUBBS
2008-07-28 20:10 ` Jim Meyering
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=1216936138.5922.62.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=gdb@sourceware.org \
--cc=jim@meyering.net \
/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