Re: Bug or Feature? Commit Selection ignored

On 5/15/07, Slim and Steve <slimandsteve@googlemail.com> wrote:

[snip]
> That's okay. Now another attempt:
>
> 1) modify foo.txt && bar.txt
> 2) call commit dialog and select foo.txt && bar.txt (or just leave
> them selected)

alternatively: open DOS box, enter
svn commit . -m "some log message"
(the dot indicates the current dir, since you want to commit everything)

> 3) standby/hibernate - wakeup cycle

not really necessary. Has nothing to do with that.

> 4) modify newfoo.txt
>
> 5) now foo.txt, bar.txt, newfoo.txt are committed (newfoo.txt should
> have not)

alternatively: hit enter in the DOS box to execute your pre-written command.
surprise: the very same thing happens!?!?

> That's not okay, but what happened to me several times this last
> year or so. It is, however, exactly what Stefan Fuhrmann described
> in his other reply, only that I should have done this test before
> posting - with three files things are a little easier to figure than with
> a whole bunch, furthermore interspersed with files not yet/never to
> be added. When it happened I never paid attention to the thought if
> I had specifically selected some files or if it happened to be all
> modified files under version control.
>
> Looks like a workaround necessitating another workaround in some
> cases. ;)

Seriously, what do you expect? You modified a file *after* TSVN
checked the files. You then simply told TSVN to commit everything
(having all files checked means everything), and it does: you just
don't see that there's another modified file there because you didn't
refresh the commit dialog (hit F5).

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