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

Re: [Subclipse-users] Remove from view problem

From: Noel Grandin <noel_at_peralex.com>
Date: 2006-03-09 14:56:44 CET

Mark Phippard wrote:

>Daniel Serodio <daniel.listas@xxx.com.br> wrote on 03/08/2006 01:11:02 PM:
>
>
>>Mark Phippard wrote:
>>
>>
>>>It is not a known issue, but now that you have said it, it would be
>>>expected. If you select a folder and choose Commit, it just does the
>>>same stuff as if you had done it from the Team menu, meaning it
>>>figures out what to commit. You could not commit stuff for multiple
>>>projects in one atomic commit if we did not do it this way. I do not
>>>recall all of the reasons we made this change, but there were some
>>>other reasons as well.
>>>
>>>
>>This behaviour bothers me too, should we file an issue to track it?
>>
>>
This is something that has bitten me lots of times - I still use the CVS
plugin a lot and in this respect, subversion does not work in the same
way at all from the Synchronize view.

Two things

(a) In the synchronize view, if you right click part of the hierarchy
and select "commit", CVS will only commit those files still present in
the tree view.

(b) Also in the synchronize view, if you right click and select
"commit", CVS will notify you if there are new (not in repository) files
and ask you if you want them to be added before it does the commit.
I still ocassionally manage to forget to commit new files because of this.

Regards,
   Noel Grandin

NOTICE: Please note that this email, and the contents thereof,
are subject to the standard Peralex email disclaimer, which may
be found at: http://www.peralex.com/disclaimer.html

If you cannot access the disclaimer through the URL attached
 and you wish to receive a copy thereof please send
 an email to email@peralex.com
Received on Thu Mar 9 15:02:11 2006

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.