Re: [Subclipse-users] Select unversioned resources on commit

On 6/5/07, Elliotte Harold <eharold@accoona.com> wrote:
> This is a defect report:
>
> The preference to "Select unversioned resources on commit" should be enabled by default.
> Repeatedly I have been bitten by committing a new file and then only later discovering that it is
> not in the repository. I am given no warning that the commit has, for all intents and purposes,
>failed.
>
> Indeed I question the wisdom of including this prefernece at all. If I select a file and commit it,
> why would I not want it to be added to the repository? I suspect this preference could be
> eliminated completely.

There was a time that it was the default and several users made
convincing arguments. Such as they had files they did not want to
commit and it is impossible to completely remove something once it was
committed etc...

The preference is needed because Subclipse allows you to select
something like your top-level project folder and take the Commit
option. It then shows all the modified/unversioned resources in the
commit dialog. I agree there are situations where we ought to do
better. For example, adding an unversioned file to a change set in
the Synch view should Add it to version control. Also if you
specifically select a resource (your example) it would also make
sense.

Feel free to file an enhancement in our issue tracker.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org