Re: Log messages (or lack thereof) in SVN

[Nicola Pero]

> > P.S.
> > And just for the record (I'll not name any names; I'd imagine you know
> > who you are), the primary violator of the "no blank commit messages"
> > suggestion has used a commit message on 4 of his last 100 commits (2 of
> > which were made today).  The diff for these same 100 commits comes to a
> > staggering:
> > 
> > 384 files changed, 59082 insertions(+), 9840 deletions(-)
> > 
> > I pray that nobody ever must decipher what has changed over the last
> > several months.
> 
> Well, these commits are only in the gworkspace repository; I was
> thinking that there are not many people interested in what has changed
> in each commit because I'm the only person that works at this project...

Eheh ... I know what you mean ;-)

... but it looks like there are actually people following what you do! ...  
:-)

Have you tried writing a very short and quick sentence every time you make
a change, like "Fixed crash in file search" or "Implemented monitoring
file changes" or something like that ?  It takes a few seconds to write it
(I personally use 'svn commit -m "Fixed crash in file search"', it works
like a charm without even opening an external editor) ;-)

If you reflect on the fact that there are people actually reading the
messages (else they wouldn't be complaining!), you might feel it's quite
nice to write them ;-)

Let's face it, you're popular ... you're a celebrity, people are watching
you and avidly reading your subversion commit messages! :-)

(actually, I'm not joking, they seem to be really reading them!)

Anyway, if you get the habit of writing a short Subversion message with
each commit, you'll find is not much in terms of burocracy overhead, and
it's quite nice.

Thanks Enrico