Re: GNUstep github mirror status...

[Gregory Casamento]

Eric,

As it turns out I probably shouldn't have used --no-metadata.   I
blindly followed some of the examples I saw since I had never done a
svn import into git before.

Luckily, I have scripts which can be used to regenerate everything in
a couple of hours.   What I will do is regenerate the repositories
with metadata.

As it turns out this will likely make committing back to the svn
repository much easier as well since it means that I will be able to
keep the svn metadata and commit back to the svn master if something
is committed into the repositories.

I will go ahead and do this tonight.

Thanks, GC

On Tue, Feb 21, 2012 at 3:13 PM, Eric Wasylishen <ewasylishen@gmail.com> 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 --grep=trunk@34124
> commit f1ff5609ca123a7f6adf59d5c06bd693ebe58850
> Author: fredkiefer <fredkiefer@72102866-910b-0410-8b05-ffd578937521>
> 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/trunk@34124 
> 72102866-910b-0410-8b05-ffd578937521
>
>
> I'd be leery of having ~100k branches/tags if a tag were made for every svn 
> revision.
>
> Eric
>
>
> On 2012-02-21, at 12:18 PM, Derek Fawcus wrote:
>
>> On Tue, Feb 21, 2012 at 01:21:58PM -0500, Gregory Casamento wrote:
>>> It looks like you're correct.  I used the following command to pull in
>>> the data from SVN:
>>>
>>> git svn clone --stdlayout --no-metadata <svnurl>
>>
>> Given the above,  and the prior discussion about svn revion ids,
>> I imagine it would be useful if we could create tags associated
>> with them,  and push those.
>>
>> e.g. svnid/r12345678
>>
>> Having a quick glance at the git-svn code,  it looks like the
>> perl would have to be hacked.  Or alternately run a background
>> script which scrapes the info from the rev_map file which looks
>> like:
>>
>> # The format is this:
>> #   - 24 bytes for every record,
>> #     * 4 bytes for the integer representing an SVN revision number
>> #     * 20 bytes representing the sha1 of a git commit
>>
>> Probably better if this can be added to the git-svn script as it
>> builds / applies the commit.  I wonder if I can figure out the
>> necessary change to 'do_git_commit' within the script - perl not
>> being my forte.
>>
>> .pdf
>>
>> _______________________________________________
>> Discuss-gnustep mailing list
>> Discuss-gnustep@gnu.org
>> https://lists.gnu.org/mailman/listinfo/discuss-gnustep
>
>
> _______________________________________________
> Discuss-gnustep mailing list
> Discuss-gnustep@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnustep



-- 
Gregory Casamento
Open Logic Corporation, Principal Consultant
yahoo/skype: greg_casamento, aol: gjcasa
(240)274-9630 (Cell)
http://www.gnustep.org
http://heronsperch.blogspot.com