[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: Alexander Klenin <klenin_at_gmail.com>
Date: 2007-01-24 04:47:02 CET

On 1/24/07, Stefan Küng <tortoisesvn@gmail.com> wrote:
> > 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.
Sounds good, and I have already understood it myself after carefully
reading design document, but how will it interact with changelists UI
in commit dialog? If changelist contains a directory, committing that
changelist will also commit all the files under that directory, which
IMHO is hard to display in the current UI.

> > 3) "Permanently local" modifications -- there are cases when developer
> > wishes to modify certain files, but does NOT plan to ever submit them
> > to repository.
> 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.

This problem is completely orthogonal to the changelists
functionality. IIUC, there is (or should be) no difference between
manually unchecking some files in commit dialog and unchecking
changelist containing said files. Changelists will hopefully just save
a few tedious "mandatory" clicks before each commit.
It would be even better if TortoiseSVN remembered the user to mark
some changelists as NOT checked by default. This way even the single
"mandatory" click would be eliminated.

As to the non-recursive commit limitation you mentioned, it is
exceptionally rare condition to want to rename/delete folder
containing (or located near) files with "permanently local"
modifications. And folders in other parts of the directory tree can be
committed just fine by starting commit in appropriate parent folder.
Finally, if the problem does arise, topic branches are still
available, just inconvenient for this purpose ;-)

Alexander S. Klenin
Insight Experts Ltd.
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Jan 24 04:47:29 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.