I'm trying to commit a big project where not all files are under version
control and only a few files have been changed.
Now when I choose commit, a whole bunch of unversioned files show up
which makes it really hard to see the real changes (what makes it even
worse, not only the unversioned directories are shown, but really all
files included in these directories).
- I can sort the files by Resource or Text Status, but not whether they
are checked or not. If I click on the first column, the list is still
sorted by Resource (Bug report)
- There is a 'Deselect unversioned' button, but I would prefer a 'Hide
unversioned' button (Feature request) - or a redesign of the commit
behavior, see below...
- Additionally I detected by accident, that selected unversioned
resources are obviously added automatically and then commited. After
explaining my problem above, I am not really convinced that this is a
good feature. I see that the way it is right now, it is easy to add and
commit all unversioned project files, but as all other subversion
clients have a different behaviour and currently no documentation of
this "feature" is available (or have I missed it?), it is really
surprising... A clearer solution I could think of is that an "Add"
button would exist in the dialog to add unversioned files - commiting
would then only be allowed if all selected resources existed already in
the repository or have been added, but not when they are unversioned.
What do you think?
Thomas
____________________________________________________________
This message may contain legally privileged or confidential
information and is therefore addressed to the named persons only.
The recipient should inform the sender and delete this message,
if he/she is not named as addressee.
The sender disclaims any and all liability for the integrity
and punctuality of this message.
The sender has activated an automatic virus scanning by
Messagelabs, but does not guarantee the virus free
transmission of this message.
Received on Wed Jan 5 02:56:51 2005