discuss-gnustep
[Top][All Lists]
Advanced

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

Re: GNUstep github mirror status...


From: Derek Fawcus
Subject: Re: GNUstep github mirror status...
Date: Tue, 21 Feb 2012 15:00:35 -0800
User-agent: Mutt/1.4.2.3i

On Tue, Feb 21, 2012 at 01:13:06PM -0700, Eric Wasylishen wrote:
> Hi Gregory,
> Thanks for doing this!
> 
> Just curious, why did you use --no-metadata? I did a personal git svn clone 
> of gui a while ago, did not specify --no-metadata, and every git commit has 
> the svn revision recorded in it.
> 
> e.g., I can grep for a given commit like this:
> 
> new-host-2:gui-git-trunk ericw$ git log address@hidden
> commit f1ff5609ca123a7f6adf59d5c06bd693ebe58850
> Author: fredkiefer <address@hidden>
> Date:   Sat Nov 5 17:45:09 2011 +0000
> 
>     Add decoding of class IBInitialTabViewItemAttribute.
>     
>     
>     git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/libs/gui/address@hidden 
> 72102866-910b-0410-8b05-ffd578937521

quite - that is garbage in the commit message;  and it seems may change if the 
SVN
repository is rehomed.

If there is another way to track these,  I'm all for it.  Using a reference 
seemed like
the simplest approach,  but one could create a parallel set of commits 
providing the
linkage,  or maybe git notes would work.

> I'd be leery of having ~100k branches/tags if a tag were made for every svn 
> revision.

Actually,  looking through things,  it would be a reference,  but not a tag or 
branch.

Probably something like refs/svnid/yyyy/xx/rrr,  so that there are not too many 
entries
in a directory.  I was thinking yyy would be 'svn.gna.org' (since revisions are 
local
to a repository),  xx would be the top 16bits of the revision and rrr the 
complete revision.


Keeping the git-svn-id line in the git commit message is (I believe) one item 
that would
make bidir sync difficult,  as it is not a fixed line.  It would be missing in 
a native
git commit,  and then added when the commit synced back from svn - branching 
the git history,
and forcing rebases.

.pdf



reply via email to

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