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

subversion transactions

From: Bosnjak Zoran ITWEP <Bosnjak_at_iskratel.si>
Date: 2005-06-23 15:32:44 CEST

Hello all,
I refer to old mail (Ben Sussman) from the subversion mailing list (see below).
Can someone please explain how can one generate and examine the transaction.

My idea of the workflow is following:
1. person A does a checkout of the main trunk
2. A makes modiffications
3. When A is about to commit, he generates a 'transaction' and sends it to B for review
4. B uses this transaction to make his working copy the same as A's and starts examine
5. B put his comments into each file property (for example), B can also correct some files itself
6. B makes a new 'transaction' out of his working copy and send it back to A
7. A updates his working copy with transaction from B
8. A makes some more corrections (comments from B)
9. Finally A makes commit to the main trunk.

Please confirm if this scenario is possible (with some extra scripting around svn). How to generate a transaction from working copy and how to apply it on someone-elses working copy (without doing actual commit to some temporary branch)?
Do you have any other idea to do formal code review before commit.

Thanks for your answer.

Zoran Bosnjak

Subversion certainly has the foundation laid out for you... in theory, a
commit transaction can live indefinitely, and a reviewer can examine it
before committing it. A simpler solution is to have people commit every
change to a real branch directory, and then have an "integrator" merge
each branch to the trunk, and then delete the branch.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 23 15:35:39 2005

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

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