On Nov 21, 11:23 am, "Andy Levy" <andy.l..._at_gmail.com> wrote:
> Do you find that this happens more frequently when you commit a
> directory after you've committed a single file, or when you're
> committing a directory which is either the parent of or not really
> related at all to the last directory you committed?
The problem happens when I make a commit in one directory and then
make a commit in a different directory that is not a parent or child
of the first.
> Remember, the revisions are global to the whole repository, so if you
> have 2 parallel directories (common parent) and commit the first
> directory, the second directory is still "behind" on revision numbers,
> even though no changes actually happened to that second directory. But
> the WC doesn't know this until you perform an update.
Yes, I totally realize that this is not a bug and that TSVN is acting
exactly how it was designed. My point is that I've requested an action
and when TSVN realized that another action needs to be taken first, a
better response would be to ask me if I want that action taken instead
of giving me instructions as to what I need to do.
> Assumptions and doing things "automatically" lead to lost work.
Well, it would hardly be an assumption at that point. If the user got
a dialog asking if TSVN should do an update first, and the user
clicked OK, then that pretty much says that the user would like to try
the commit again if the update doesn't unveil any new issues. Hell,
make the dialog say "Do an update and then retry the commit if there
are no conflicts?" Anything like that would be nicer than an error
message telling me what I should do. :)
Gre7g
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-11-21 19:54:24 CET