[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Transaction building with bindings, do I need a WC on disk

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-02-24 04:20:43 CET

On Feb 23, 2005, at 6:16 PM, Travis P wrote:

>
> I've a couple question regarding what's generally possible that I
> think some developers could probably answer pretty quickly.
>
> If I'm using the Python (or Perl I imagine; thus far I just built
> Python) bindings, can I build a transaction on the server-side
> in-memory. I essentially want to merge a change into another location
> automatically iff it is conflict-free because the original files are
> identical (guaranteed conflict-free merge).
>
> In this instance, each release generally contains about 8000 files and
> is about 35 Mb. Many commits to trunk (usually of <= 20 files) will
> automatically need to commit to 2 or 3 releases.
>
> One idea would be to only checkout some things -- i.e. use
> non-recursive checkouts -- which could be a huge savings in most
> instances, but from what I've seen reported to the mailing lists here,
> non-r checkouts suffer some significant bugs.
>
> Maybe if I build a very selective WC myself with the bindings, the
> non-r checkout-related bugs won't rear themselves?
>
> Any ideas about all this?
>

My reaction is: I don't understand the bigger picture, and why you're
trying to do such complex things.

AFAICT, you need to port a 'set of changes' from the trunk to N
different release branches. Why can't you do it the normal way? Keep
a working copy of every release branch. Run 'svn merge' on each one,
and then 'svn commit'.

That's how changes get ported from one branch to another in Subversion.
  I don't see what -N checkouts have to do with anything, or why you're
trying to copy files around between branches. I'm wondering if you're
trying to artifically transfer a paradigm from some other SCM system to
Subversion.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 24 04:22:25 2005

This is an archived mail posted to the Subversion Dev mailing list.