FW: inconsistency in the vendor branch examples

I sent this to svnbook-dev@red-bean.com but never heard back. Was that a
waste of time?

Anyways, am I off base here?

JLM

From: Jeremy Mordkoff
Sent: Wednesday, October 03, 2007 4:20 PM
To: svnbook-dev@red-bean.com
Cc: Jeremy Mordkoff
Subject: inconsistency in the vendor branch examples

In General Vendor Branch Management Procedure

We now have the current version of the libcomplex source code in
/vendor/libcomplex/current. Now, we tag that version (see the section
called "Tags"
<http://svnbook.red-bean.com/en/1.4/svn.branchmerge.tags.html> ) and
then copy it into the main development branch. Our copy will create a
new directory called libcomplex in our existing calc project directory.
It is in this copied version of the vendor data that we will make our
customizations.

$ svn copy http://svn.example.com/repos/vendor/libcomplex/current \
           http://svn.example.com/repos/vendor/libcomplex/1.0 \
           -m 'tagging libcomplex-1.0'
...
$ svn copy http://svn.example.com/repos/vendor/libcomplex/1.0 \
           http://svn.example.com/repos/calc/libcomplex \
           -m 'bringing libcomplex-1.0 into the main branch'
...

But later on in svn_load_dirs.pl

You can indicate that you'd like svn_load_dirs.pl to tag the new vendor
drop by passing the -t command-line option and specifying a tag name.
This tag is another URL relative to the first program argument.

$ svn_load_dirs.pl -t libcomplex-1.1 \
                   http://svn.example.com/repos/vendor/libcomplex \
                   current \
                   /path/to/libcomplex-1.1
...

To be consistent with the above, shouldn't this be just "-t 1.1"

JLM

____________________

Zazzle Technologies, Inc

238 Littleton Road, Suite 200

Westford, MA 01886

978-467-1395 x233

 
Received on Tue Oct 9 14:24:17 2007