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

Subversion utilities

From: Anil Arora <anil_at_interlacesystems.com>
Date: 2004-05-11 20:35:22 CEST

Hi, all.


I've been testing subversion for the last month, and I definitely like it a
lot better than VSS which we are currently using.

After coming from a company that used Perforce, I'm finding a lot of
inconveniences with Subversion. In particular, the branching/merging stuff
is a little painful.


Each developer is working in their own branch off the trunk and routinely
needs to merge changes from the trunk into the branch (I tend to do this
once every two days). Also, the reverse will be needed when developers want
to merge their branch into the trunk. It's seems inconvenient to have to
remember the revision number for the last merge, everytime. Couldn't
subversion keep track of this information automatically so that I don't have
to specify the revision when I run svn merge?

As a workaround, I was thinking of writing some perl script to wrap around
the svn merge to keep track of the merge points in a file that is also
checked into subversion at some particular location. It's basically a hack,
but it would get me around this pain point.


Before I start writing my own scripts to hide these inconveniences in
subversion, I wanted to see what people have come up with that could help.

Is there some user-contrib repository that I can contribute/download from?
I see references in the "post-commit.tmpl" file to "commit-email.pl" and
"log-commit.py" scripts. Do those files exist somewhere?




Received on Tue May 11 20:37:51 2004

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.