"thomas mauch" <Thomas.Mauch@swisslog.com> wrote on 01/04/2005 10:56:51
AM:
> 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)
I will see if it is possible to sort by checked or not. Why can't you
just sort on the text status column. That would group the unversioned
items from the modified items.
> - 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...
We wanted to make it work that way but it would have been difficult.
Personally, I didn't see any reason for it in Eclipse. Derived files are
ignored automatically, and there are two other mechanisms to ignore files.
What is the scenario that you need to have a lot of unversioned files in
your project but you cannot just use an ignore mechanism to filter them
out?
> - 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?
I obviously think the current behavior is the ideal, or I wouldn't have
made it work that way. I do not understand why what happens is
surprising. We modelled the behavior off TortoiseSVN which also works
this way. The only thing we did differently was that we made unversioned
files selected by default for the reasons I said previously.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Wed Jan 5 03:05:05 2005