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

Re: 1.5 beta: Change list feature

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Tue, 25 Mar 2008 21:52:38 +0000

On 25/03/2008, Hautzenroeder, Brenna M <bmhautz_at_sandia.gov> wrote:
> I've been playing around with the beta (and alpha) version of 1.5.0, and I
> must say, I like the new features a lot! However, the new change lists
> feature seems a bit odd to me; here's why:
> 1) I expected that the change list option would have been added to the
> normal TortoiseSVN context menu, not the commit dialog. I can sort of see
> the reason for this since it is tightly coupled with commits; however, the
> change list feature now seems limited in its flexibility (i.e. I can't add
> file(s) to a particular change list in the middle of a major edit without
> invoking the commit dialog - which seems counterintuitive).


You can also use the Check for Modifications dialog.

> 2) I find it frustrating, though, that I have to actually edit the file
> before I add it to a change list. It seems that I have to retroactively
> assign files to a change list after being edited as opposed to starting with
> a set of files in a change list and then proceeding with the common set of
> changes.

It is possible from the CfM dialog, but you have to use the 'Show
unversioned files' checkbox. That would not work well on a large tree.
Unless we add changelists to the general menu I don't see much mileage
in this.

> This approach also seems useless in the case where I make one
> major edit across several related files and then commit it - no need for a
> change list here as far as I can tell.

Well no feature is going to be useful in every situation. To be
honest, a lot of the Subversion developers are unsure about the
usefulness of changelists, but it was an easy feature to add and seems
to be aimed at those familiar with Perforce.

> 3) It also seems that I can't add files to a change list after the change
> list has already been created:
> 1 - Assign two files to a change list, let's call it MyEdits, and either
> commit or cancel commit.
> 2 - Try and add another file to a change list, in particular, MyEdits.
> All of the available change lists in Move To Changelist are <new changelist>
> and ignore on commit - so it seems that the creation of a change list is a
> one time deal.

I can't reproduce this, although I'm still using r12283.

> 4) After I've added a file to a change list (we'll stick with MyEdits), I
> click on the Subversion tab under the file's properties and see that MyEdits
> is shown as the Repository UUID value instead of the Changelist value (which
> is empty). This seems like a bug, but I also don't know what each value
> truly represents.


> 5) The documentation for this new feature (so far) is only about 2
> paragraphs and doesn't really go into much use-case or implementation
> details. It doesn't even mention the Keep Changelists checkbox!

My bad. I will take a look.

> Whew! :) I doubt whether any of the above points could be integrated into
> the code before the actual 1.5.0 release or if it's even deemed desirable to
> do so for a later release; or maybe I'm missing the point of the change
> lists feature all together. However, at the very least, it seems that the
> documentation could be beefed up a bit to give users a better idea of how to
> maximize this new feature in their daily activities (and how to properly
> implement it).

You may yet be surprised by ATITSTFAB :-)


  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org
Received on 2008-03-25 22:52:53 CET

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