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

Re: Changelists overview?

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2007-01-23 21:56:25 CET

Alexander Klenin wrote:

> Below are my use cases for subversion changelists:
> 1) Working on two or more issues in the same working copy. This is
> actually the LEAST compelling of the use cases, to the point where one
> might argue that topic branches must be used instead, and VCS should
> not encourage sloppy software development practices.
> However, because Subversion is a centralized VCS, in the case of
> temporarily lost connection changelist might come handy. In fact, this
> is a primary motivation to Subversion developers, according to their
> design document:
> http://svn.collab.net/repos/svn/trunk/notes/changelist-design.txt

And that's also what it is designed for.

> 2) Simplifying commit separation -- many projects have layered
> architectures with supporting polices. In particular, it is often
> required to commit changes to each layer separately. New Tortoise UI
> might help greatly here -- the only worry I have is that changelists
> seem to include only files, while I want to also use directories
> and/or file masks.

Changelists can also include folders. You need to use the
check-for-modifications dialog and check the "show unmodified files"
checkbox. Then you will also see all the folders and you can add them to
a changelist if you like.

> 3) "Permanently local" modifications -- there are cases when developer
> wishes to modify certain files, but does NOT plan to ever submit them
> to repository. The most frequent cases are probably debugging
> modifications and local configuration modifications. Again, I have a
> worry here -- it seems that there is no way to exclude a change list
> from commit. At least that problem can be rather easily solved on
> Tortoise level.

Sorry, but you should *not* use changelists for this!
Because: committing only a subset of modifications requires a
non-recursive commit. And non-recursive commits are limited. For
example, you can't commit a folder deletion or a moved folder with a
non-recursive commit - only a recursive commit can do that.
Which means: if you want to use changelists to exclude certain versioned
files from never getting committed, you will have a problem as soon as
you delete or rename/move a folder.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Jan 23 21:56:38 2007

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

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