[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: git repository with fixed history ready

From: Jan Nieuwenhuizen
Subject: Re: git repository with fixed history ready
Date: Tue, 23 Mar 2010 16:59:28 +0100

Op maandag 22-03-2010 om 18:14 uur [tijdzone -0700], schreef Patrick
> On 2010-03-22, Jan Nieuwenhuizen wrote:

> Wow, this is very awesome!  That must have been a tremendous effort.  :)


> Just a side note:  cloning over HTTP by default is really inefficient
> right now, so the download size of the above repo is ~900MB.  After
> running `git gc --aggressive', the repo shrinks to the normal size
> (~120MB).

Hmm, I saw that before and think I'd taken care of that.  Ah, I
see, only after the first stage.  I'm adding that, thanks.

> This is mostly true.  There are still some random commits that have
> CVS-style usernames.  For example, in the new repo,
>   $ git show bc86bf
> displays
>   commit bc86bf019ae3d2f03c12e8b52527bd5eb48283f3
>   Author: jneem <jneem>

Ugh.  Then I'm missing some still.  Oh, I only rewrote
the CVS era, I should check/rewrite the GIT history

> But, overall, there are relatively few of these cases.  Most of them
> have been fixed.

Yes, well, let's fix them all now :-)  I've put-up a new
version, but if you have suggestions for
in please send
a patch ;-)

> I'm generally okay with this.  Of course, it would be optimal to fix
> only the "pre-Git" part of LilyPond's history, but I imagine that
> would take a lot of work.

Uh, that cannot really be done, all pre-git is in the current
archive too - if you want to cut that out, all committishes change

> Thanks a lot, Jan.  This will be incredibly helpful for the Ohloh
> project page, too.

Yes, but I'm not sure if Ohloh is all that useful ;-)

Also, email addresses will change in the future, it's just
nice that totally unattributable fred@ is gone :-)


Jan Nieuwenhuizen <address@hidden> | GNU LilyPond - The music typesetter
AvatarĀ®:    |

reply via email to

[Prev in Thread] Current Thread [Next in Thread]