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

Re: Unclear: CVS and Subversion repository difference.

From: Dirk Schenkewitz <schenkewitz_at_docomolab-euro.com>
Date: 2005-06-17 19:43:41 CEST

Ben Collins-Sussman wrote:
> [please keep this discussion on the list]

Sorry, I forgot "answer to all" and wondered why it didn't show up on the
list. I'll slap myself for being so stupid.

> You run 'svn log' and find the commits for the bugfix or feature. Then
> you 'backport' those specific revisions to a 1.1.3 working copy (or a
> branch of 1.1.3).
> There's a description of subversion's own release management process in
> the book here:
> http://svnbook.red-bean.com/en/1.1/ch04s04.html#svn-ch-4-sect-4.4.1
> The last step of the process is similar to what you're describing.

In my case, I could simply tag the revision before feature B was aded as
"1.1.3-A", given that there was no bugfix later on. Then I could just
compile that version and give it to the customer, no need to backport

I was hoping for some trick to find the right version faster than just
looking thru all that 'svn log' gives me... Hmm. 'svn log -v' from
within a tag directory shows from what path and revnum TAG was copied.
I could begin the scan for the best revnum to tag from there on, that
would at least narrow the search.

Thank you very much for that hint!

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 17 19:45:34 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.