Stefan Küng wrote:
> Gre7g wrote:
>> I'm the only programmer developing one of the projects I'm on, but
>> quite often I'll attempt a commit and TSVN will spit back a "working
>> directory is out of date, please do an update first" sort of message.
>> This seems kind of silly to me as I know that no one has made changes
>> to the files involved, but oh well. I do an update and then a
>> recommit.
>>
>> Yes, it's not a big deal to do an update and recommit (especially
>> since TSVN saves log messages), but considering how often this
>> happens, wouldn't it be a good idea for TSVN to actually look for this
>> error specifically? Instead of just returning the error and dumping it
>> all back on me, TSVN could just pop up a dialog saying "TSVN needs to
>> do an update first. Update now?" The user could click OK or Cancel. On
>> OK, TSVN would do an update of the appropriate directory and then if
>> no new conflicts were found, pop up a second dialog saying, "Update
>> complete... Try the commit again?"
>>
>> Or, hell, just assume "yes" at that point and do the commit again with
>> the log message the user already entered. If conflicts were found,
>> just pop up an informational dialog so the user knows why the commit
>> wasn't retried.
>
> http://subversion.tigris.org/faq.html#wc-out-of-date
That information is great, but I don't think the OP is talking about
being confused - they're talking about a way in which the software could
make life easier without any real likelihood of causing problems. If the
error in question is detected, just provide an "easy option" to
immediately do an update followed by a retry of the commit (if the
update is flawless). Don't do it without asking, but offer to. I'd find
it useful.
--
Sam Barnett-Cormack
---------------------------------------------------------------------
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 22:48:10 CET