Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Meyering <jim@meyering.net>
To: Thiago Jung Bauermann <bauerman@BR.IBM.COM>
Cc: gdb@sourceware.org
Subject: Re: gdb.git: author username-to-Full_Name+email map: RFC
Date: Fri, 25 Jul 2008 13:41:00 -0000	[thread overview]
Message-ID: <87abg6nya4.fsf@rho.meyering.net> (raw)
In-Reply-To: <1216936138.5922.62.camel@localhost.localdomain> (Thiago Jung 	Bauermann's message of "Thu, 24 Jul 2008 18:48:58 -0300")

Thiago Jung Bauermann <bauerman@BR.IBM.COM> wrote:
...
> Do you know if there will be disruption if GDB moves to Subversion?

There would be some disruption, because the current
synchronization method is tied to GIT and CVS.
But it wouldn't be too bad, since git-svn provides
trivial bi-directional access.
Any branches relative to the cvs-derived git repo
could be migrated to a git repo converted from svn.

Of course, any SHA1 references into the cvs-derived repo
would be worthless (but they could theoretically be translated
to point to the same objects in an svn-derived repo).

>> 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.

Good to know it works.  Thanks.


  reply	other threads:[~2008-07-25  8:50 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
2008-07-25 13:41   ` Jim Meyering [this message]
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=87abg6nya4.fsf@rho.meyering.net \
    --to=jim@meyering.net \
    --cc=bauerman@BR.IBM.COM \
    --cc=gdb@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