I'm with Kurt on this one. I do have some trouble convincing others here of
the value of this exercise, but it is _very_valuable_.
I click the commit, then visit _every_ file with tsvn diff/merge to make
sure that all the changes I expect are there and no unexpected changes are
there. As I review the changes, I generate my log entry. If a file that is
not associated with the changes I'm committing is found, I just un-check it
and leave it for another commit.
It seems time consuming, but the 15 minutes spent saves hours within weeks
(if not days.)
?EYPO?
Donald.
Kurt Pruenner wrote:
> Andy Levy wrote:
>> Cameron Stone wrote:
>>> I would like tortoise to have a simple text dialog in which I can type
>>> notes about what I'm currently doing to the code. Thus, when I get to my
>>> next commit, I have the log message pre-written (though maybe in need of
>>> some editing). Perhaps the contents of this dialog could be pre-loaded
>>> into the commit log text area when the commit dialog is started.
>> Do you frequently leave a TSVN window open while you're working with your code?
>>
>> I have to agree with Kevin, this really sounds like bloat & feature
>> creep with no obvious advantage over keeping a text editor open.
>
> Personally, I use the commit window to revisit all changes I've made to
> the code (by opening a diff for each changed file and going over it
> again) and write the changelog as I go along.
>
> This helped me find some mistakes at the last possible moment, and it
> also means I can just hack away at the code without having to document
> every change immediately, which I'd find rather distracting...
>
> Just my 0.02 EYPO...
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-02-27 13:55:09 CET