[Cosmo-dev] svk for sandbox sync?

[Grant Baillie]

On 20 Sep, 2006, at 15:23, Travis Vachon wrote:

> I configured svk this morning, and have a setup I'm pretty happy with.
>
> I've made a mirrored checkout, a local checkout, and a working  
> copy. The
> working copy is checked into my svn sandbox. To merge in trunk  
> changes,
> I use svk to merge into my working copy and svn to commit the working
> copy to my sandbox.
>
> I'll put something up on the wiki soon about this, but hopefully that
> helps for now.

While people are plugging svk: I've been using svk it for a month  
now, and am very happy. For each separate feature I work on, I create  
a copy of the mirrored source tree, and can merge ("smerge" is the  
svk command) from the mainline at will. I had a local branch of  
chandler that I was copying out to my svn sandbox every day or two,  
and svk really made that straightforward.

So far as docs go, the online book is still pretty sketchy (really  
just a rehash of the not very complete man pages), but there seems to  
be a lot of info out on the web. In particular, I found the following  
very helpful:

http://www.bieberlabs.com/wordpress/archives/2004/11/30/using-svk

as well as other links in that dude's "svk" category.

--Grant

> Jared Rhine wrote:
>> Brian Moseley wrote:
>>
>>> grant mentioned that he's been using svk (<http://svk.elixus.org/ 
>>> >) to
>>> keep his sandbox in sync with the chandler turnk. maybe this  
>>> would be
>>> useful for travis and vinu as well?
>>>
>>
>> I'm using svk to keep track of patches to the Cosmo trunk.  This is a
>> different configuration than tracking back to a sandbox that you  
>> can check
>> in to, but my mostly-self-reminder notes are available here:
>>
>> http://wiki.osafoundation.org/bin/view/Journal/SvkUsageNotes
>>
>> To do what you describe, you'd make two mirrored checkouts, two  
>> local ones,
>> and be able to diff between I think any of those (since they are  
>> all inside
>> one svk repo).
>>
>> svk is handy for normal committer development too.  Faster for most
>> operations since it's got a full local copy to act against.
>>
>> -- Jared
>> _______________________________________________
>> cosmo-dev mailing list
>> cosmo-dev at lists.osafoundation.org
>> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev
>>
>
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev