Re: svn commit: rev 2892 - trunk/subversion/mod_dav_svn

Ben Collins-Sussman <sussman@collab.net> writes:
> Oops, you're right, sorry for being so verbose.
>
> I often get annoyed when I see a log message that has nothing but a
> list of file/symbol change descriptions, and is missing a "one
> sentence summary" at the top. I want to know the general intent of
> the patch *before* reading about particular changes to symbols.

It was a great summary, and made it much easier to understand the
change itself. I suppose it would have been as helpful had its text
appeared in the patch... But it's not a problem that it appeared in
the log message, only that it *didn't* appear in the patch itself.

> But my great weakness is to go too far in the other direction. My
> one-sentence summary ends up being an essay. :-(
>
> There's no need to put my log msg in the code. The code is obvious.
> My verbiage is nothing but a feature description, better moved to the
> Handbook... which I'll do.

No no -- it's a fine summary for the logs too, I'm just saying that
that content also belongs in the code and/or in the documentation.

I think that excerpt from HACKING didn't reflect what I really wanted
to say, sorry for being unclear.

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 6 17:20:26 2002