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

[Subclipse-users] RE: Feature Request: "add to ingnore list" in commit dialog

From: Eduard Wirch <ew_at_omikron.net>
Date: 2007-03-22 20:55:09 CET

Hi Mark

> I cannot say I am close to coding changes like this, but what do you think
about that?  For people that adopt this workflow, I do think it offers
better usability.

Good point. I love to use the synchronize view. But still: the import
remains uncomfortable. It is split up in two steps:
- creating the project folder in repository and bind the project to the
source control system and
- commit the files to repository
There is a bin directory with a lot of classes in there which I don't want
to commit. It would be enough for me if I could deselect the bin directory,
all of its subdirectories and files with one action in the commit dialog. So
I don't have to cancel the import process, add the bin directory to ignore
list, and commit the files than.

Cheers,
Eduard

________________________________________
Von: Mark Phippard [mailto:markphip@gmail.com]
Gesendet: Donnerstag, 22. März 2007 12:52
An: users@subclipse.tigris.org
Betreff: [Spam] [Hit=6,93] Re: [Subclipse-users] Feature Request: "add to
ingnore list" in commit dialog

On 3/22/07, Eduard Wirch <ew@omikron.net> wrote:
Hi all
 
I'll like to request a feature which would make it possible to exclude (add
to ignore list) directories/files directly out of the commit dialog. Like it
is already supported by Tortoise. This would make life easier especially
when importing new projects.
 
What do you think about this?
I have lately been hearing the opposite feedback, that we should remove
almost all features like this from the commit dialog and make it more like
the CVS dialog where it just lists your files and lets you type a commit
message.  I think this comes from people that have adopted the workflow of
using the Synchronize view for most actions.  In that scenario, the Synch
view serves the purpose of those features and the commit just becomes a step
where the message is all that is needed and the rest is just redundant.

I cannot say I am close to coding changes like this, but what do you think
about that?  For people that adopt this workflow, I do think it offers
better usability.

As for your idea, to do something like that it would be doable, but a major
change.  Because it would mean we would also have to change the dialog to be
listening for changes in the working copy and possibly updating the dialog
as a result.  This would be a major change in terms of complexity.

-- 
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
Received on Thu Mar 22 20:55:18 2007

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.