[Vm-dev] equivalent of svn export...

Eliot Miranda eliot.miranda at gmail.com
Tue Jun 28 16:10:50 UTC 2016


Hi Esteban,

> On Jun 28, 2016, at 12:21 AM, Esteban Lorenzano <estebanlm at gmail.com> wrote:
> 
> Hi, 
> 
> 
>> On 28 Jun 2016, at 02:57, Ben Coman <btc at openInWorld.com> wrote:
>> 
>> I'm not at a computer where I can test this, but in summary I would just try...
>> $ git checkout -b splitARM Cog
>> $ mv build.linux32ARM build.linux32ARMv6
>> $ cp -r build.linux32ARMv6 build.linux32ARMv7
>> $ git add build.linux32ARMv6 build.linux32ARMv7
>> $ git commit -m "Split ARM build into ARMv6/ARMv7"
>> $ git diff -M -C --summary Cog
> 
> I’m not sure either what’s the purpose of checking out just a directory… in git, since it does global versions for commits, it does not has much sense… also git is designed to do the branching a very easy/efficient task open a new branch… and then merging back is a second-time task). 

At Cadence there are automatic build of only VMs derived from nsspursrc and only on build.linux32x86, so when we were on subversion we would check out these and processors and build and save time and space.  Now we have to check out the whole thing.

> So I suppose this is the right way to do it… I imagine that different tools means sometimes different ways of doing things, and forcing “old way” can be not as effective as it was before. 
> 
> +1 for this step list :)
> 
>> You might first want to
>> $ cp -r oscogvm oscogvm.practice
> 
> why? if you made a mistake you can just kill the branch :)

+1

> 
> Esteban
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20160628/28a9222e/attachment.htm


More information about the Vm-dev mailing list