[message below - anyone else dislike bottom-posting?]
Cameron Stone wrote:
[snips]
>
> I too use the "commit dialog as code review and log message creation" as
> Kurt and Simon described. It's sensible to review your code, thus, but
> it seems foolish to "hack away", then later try to remember what you
> were doing when you commit, when it would be so trivial to jot down your
> intentions. This is just my opinion, though, and I realise that others
> have different code management strategies.
The easiest and most reliable thing to do is to "jot down your intentions"
in the code. That is what the comments in code are for. (Anyone can read
code to see what it's doing; very few can (can anyone??) read uncommented
code and discern the programmer's intent!!!) When you are reviewing your
changes at checkin time, all your notes are right there, you can copy and
paste them from the diff/merge window and build your commit log message.
JMO, (Just My Opinion)
Donald.
>
> Personally, I think I would use this feature, but obviously if I'm the
> only one, then it's not worth adding.
>
> TortoiseSVN is great, BTW.
>
> Cameron.
---------------------------------------------------------------------
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 14:04:05 CET