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

RE: Re: Holding commits till review

From: Bill Tutt <rassilon_at_lyra.org>
Date: 2002-08-06 20:00:31 CEST

> From: Wilfredo Sanchez [mailto:wsanchez@mit.edu]
> Writing these with SVN may actually be harder, though, since
> are
> not really an SVN mechanism, and the scripts would have to figure out
> your
> branching tree structure (/branches/XXX or /project/branches/XXX ...?)
> before proceeding to make/find a branch by name. I guess it may have
> take
> full paths to branches.

In Subversion, the name of a branch is the full path to the branch.

> The problem with the idea of using transactions is that it's not at
> clear
> how you'd deal with the case where the code is denied pending some
> The developer then needs to edit the transanction (probably not
> or
> create a new one. And what happens to the working copy when a
> is
> accepted but not commited? If it is edited further and another commit
> comes
> along but the first txn is still in limbo?

Actually, it's perfectly conceptually feasible to edit a Subversion
transaction, but we're certainly not going to write the code to do that
for 1.0. The data model supports this kind of stuff quite easily.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 6 20:01:46 2002

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.