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

Re: Bug or Feature? Commit Selection ignored

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2007-05-16 12:56:31 CEST

On 5/16/07, Slim and Steve <slimandsteve@gmail.com> wrote:
> Stefan Küng <tortoisesvn <at> gmail.com> writes:
>
> [big snip]
>
> > http://issues.tortoisesvn.net/?do=details&task_id=339
>
> Thanks, Stefan.
>
> For the solution some different suggestions, however:
>
> A) Just treat the checkmarked/selected files/folders as a list and process it
> just as svn ci -F <filelist> would do. No file system monitoring necessary.

Not possible. If we would do that, then we'd have to stick to
non-recursive commits. And non-recursive commits can't commit folder
deletions.
--> we *must* commit recursively if the user has everything selected.

> B) With file system monitoring: on refresh of commit dialog add new modified
> files *un*selected/checked and issue an alert message so the user can decide how
> to deal with the situation (either commit as selected before or check the file
> list first again.

I was thinking more of having the monitoring thread set a flag, and
when the user clicks ok show a message that the contents have changed.
Automatically refreshing is not good, and interrupting the user with a
messagebox while he may be writing a log message isn't good either.

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed May 16 12:56:55 2007

This is an archived mail posted to the TortoiseSVN Dev mailing list.