Re: Offer of help with move to git

On 24 August 2015 at 09:40, Tom Tromey wrote: > Eric> In the mean time, I'm enclosing a contributor map that will need to be > Eric> filled in whoever does the conversion. The right sides should become > Eric> full names and preferred email addresses. > > It's probably worth starting with the map

GCC branches/st (was Re: Offer of help with move to git)

[David, we're talking about moving the GCC repository to Git, and how to handle subdirectory branches.] On 09/04/2015 12:17 PM, Joseph Myers wrote: branches/st is more complicated than simply being a container for subdirectory branches. It has a README file, five cli* subdirectories that look

Re: Offer of help with move to git

On Thu, 27 Aug 2015, Jason Merrill wrote: > Unfortunately, it looks like reposurgeon doesn't deal with gcc SVN's > subdirectory branches any better than git-svn. It does give a diagnostic > about them: > > reposurgeon: branch links detected by file ops only: branches/suse/ > branches/apple/ bran

Re: Offer of help with move to git

On 08/28/2015 12:13 AM, Eric S. Raymond wrote: With respect to Joseph's point about periodic deletion and re-creation of branches, it looks like reposurgeon dutifully models them as deletion and re-creation of the entire tree, which is understandable but not ideal. It also warns about these with

Re: Offer of help with move to git

On 08/27/2015 10:13 PM, Eric S. Raymond wrote: I'd like to use the --legacy flag so that old references to SVN commits are easier to look up. Your call, but ... I don't recommend it. It's very cluttery, and I've found the demand for that kind of lookup tends to drop off after conversion faster

Re: Offer of help with move to git

Jason Merrill : > First, thanks a lot for the offer of help; I'm happy to take you up on it > rather than do it all myself. One important and messy part is just winding up - assembling a contributor map so we'll have proper DVCS IDs everywhere. > On 08/24/2015 12:54 PM, Joseph Myers wrote: > >FWI

Re: Offer of help with move to git

First, thanks a lot for the offer of help; I'm happy to take you up on it rather than do it all myself. On 08/24/2015 12:54 PM, Joseph Myers wrote: FWIW, Jason's own trial conversion with reposurgeon got up to at least 45GB memory consumption on a 32GB repository. It ended up being about 65GB

Re: Offer of help with move to git

On 08/24/2015 01:46 PM, Frank Ch. Eigler wrote: Joseph Myers writes: [...] FWIW, Jason's own trial conversion with reposurgeon got up to at least 45GB memory consumption on a 32GB repository. (The host sourceware.org box has 72GB.) And if Jason really needs it, we've got considerably larger

Re: Offer of help with move to git

Joseph Myers writes: > [...] > FWIW, Jason's own trial conversion with reposurgeon got up to at least > 45GB memory consumption on a 32GB repository. (The host sourceware.org box has 72GB.) - FChE

Re: Offer of help with move to git

Joseph Myers : > FWIW, Jason's own trial conversion with reposurgeon got up to at least > 45GB memory consumption on a 32GB repository. I have no trouble believing that at *all*. -- http://www.catb.org/~esr/";>Eric S. Raymond

Re: Offer of help with move to git

On Mon, 24 Aug 2015, Eric S. Raymond wrote: > Joseph Myers : > > Hence my suggestion in > > of reconverting and then combining with the existing git-svn history via > > renaming all the refs in the existing git repository, so as to preserve > >

Re: Offer of help with move to git

Joseph Myers : > Hence my suggestion in > of reconverting and then combining with the existing git-svn history via > renaming all the refs in the existing git repository, so as to preserve > the validity of commit references and git-only branche

Re: Offer of help with move to git

Tom Tromey : > Eric> In the mean time, I'm enclosing a contributor map that will need to be > Eric> filled in whoever does the conversion. The right sides should become > Eric> full names and preferred email addresses. > > It's probably worth starting with the map I used when converting gdb. > Th

Re: Offer of help with move to git

On Sun, 23 Aug 2015, Andreas Schwab wrote: > Florian Weimer writes: > > > Okay, it's not a big deal for me if my older contributions are > > attributed to Red Hat. I was just wondering. > > Since subversion doesn't store author names, only committer names, the > real attributions are in the Ch

Re: Offer of help with move to git

On Sun, 23 Aug 2015, Eric S. Raymond wrote: > Whoever you designate to lead the conversion *should read this Jason Merrill is leading the conversion. > Hwew's a particular warning: though you may be using git-svn for live > gatewaying, it is *not* the way to go for full-history conversions, as

Re: Offer of help with move to git

Eric> In the mean time, I'm enclosing a contributor map that will need to be Eric> filled in whoever does the conversion. The right sides should become Eric> full names and preferred email addresses. It's probably worth starting with the map I used when converting gdb. There is a lot of overlap b

Re: Offer of help with move to git

DJ Delorie : > > > In the mean time, I'm enclosing a contributor map that will need to be > > filled in whoever does the conversion. The right sides should become > > full names and preferred email addresses. > > This information should be gleanable from the Changelog commits... > do you have a

Re: Offer of help with move to git

> In the mean time, I'm enclosing a contributor map that will need to be > filled in whoever does the conversion. The right sides should become > full names and preferred email addresses. This information should be gleanable from the Changelog commits... do you have a script to scan those?

Re: Offer of help with move to git

Markus Trippelsdorf : > On 2015.08.23 at 11:36 -0500, Segher Boessenkool wrote: > > On Sun, Aug 23, 2015 at 12:26:25PM -0400, Eric S. Raymond wrote: > > > One way to do it would be to mine the list archives for not just names > > > but name-date pairs. With a little scripting work that could be pro

Re: Offer of help with move to git

Segher Boessenkool : > On Sun, Aug 23, 2015 at 12:26:25PM -0400, Eric S. Raymond wrote: > > One way to do it would be to mine the list archives for not just names > > but name-date pairs. With a little scripting work that could be processed > > into a sequence of map files, each one valid for a kno

Re: Offer of help with move to git

On 2015.08.23 at 11:36 -0500, Segher Boessenkool wrote: > On Sun, Aug 23, 2015 at 12:26:25PM -0400, Eric S. Raymond wrote: > > One way to do it would be to mine the list archives for not just names > > but name-date pairs. With a little scripting work that could be processed > > into a sequence of

Re: Offer of help with move to git

Florian Weimer writes: > Okay, it's not a big deal for me if my older contributions are > attributed to Red Hat. I was just wondering. Since subversion doesn't store author names, only committer names, the real attributions are in the ChangeLog anyway. Andreas. -- Andreas Schwab, sch...@linu

Re: Offer of help with move to git

On Sun, Aug 23, 2015 at 12:26:25PM -0400, Eric S. Raymond wrote: > One way to do it would be to mine the list archives for not just names > but name-date pairs. With a little scripting work that could be processed > into a sequence of map files, each one valid for a known span of dates. The > only

Re: Offer of help with move to git

Florian Weimer : > * Eric S. Raymond: > > > Florian Weimer : > >> Thanks for your offer for working on this. (I actually brought up > >> your name at the Cauldron. :) > >> > >> Can your tools handle changes in preferred email addresses over time? > > > > It would in theory be possible to do this

Re: Offer of help with move to git

* Eric S. Raymond: > Florian Weimer : >> Thanks for your offer for working on this. (I actually brought up >> your name at the Cauldron. :) >> >> Can your tools handle changes in preferred email addresses over time? > > It would in theory be possible to do this with multiple applications > of th

Re: Offer of help with move to git

Florian Weimer : > Thanks for your offer for working on this. (I actually brought up > your name at the Cauldron. :) > > Can your tools handle changes in preferred email addresses over time? It would in theory be possible to do this with multiple applications of the reposurgeon "authors read" co

Re: Offer of help with move to git

* Eric S. Raymond: > In the mean time, I'm enclosing a contributor map that will need to be > filled in whoever does the conversion. The right sides should become > full names and preferred email addresses. Thanks for your offer for working on this. (I actually brought up your name at the Cauld

Offer of help with move to git

I learned on G+ that there's discussion of moving the GCC repository to git going on. Some of you might already be aware that I did both the groff CVS -> git conversion and the Emacs bzr -> git conversion, and am pretty much the go-to guy for high-quality conversions of important projects. Since