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

Re: Vendor Branch Here

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Wed, 16 Oct 2013 19:13:49 +0200

On 16.10.2013 02:18, Gavin Lambert wrote:
> I just noticed this new feature listed in the release notes for 1.8
> ("Third Party Libraries"). It doesn't appear to be covered in any of
> the other documentation as far as I can tell, so I was wondering about
> the specifics of how it works.
> The release notes just briefly say "TortoiseSVN then scans both
> directories, copies all new files, removes files that are not present
> anymore in the new version."
> Does it just do literally that and no more, or does it work more like
> svn_load_dirs.pl with interactive discovery of renames?

It does exactly that and no more.

> Presumably it does not preserve local edits either (as I can't see how
> it could without having a reference unmodified copy of the previous
> vendor drop). Isn't this the most important feature of vendor branches?

It's for vendor branches, which should not have local modifications.
IMHO if you have to change/modify an external lib, create a patch from
your changes and have that patch somewhere versioned as well. Then after
upgrading the lib (using the vendor branch command) you can apply the
patch again to that new version.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest interface to (Sub)version control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-10-16 19:14:02 CEST

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

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