You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by Michael Parker <pa...@pobox.com> on 2004/09/15 14:30:20 UTC
Re: svn commit: rev 46098 - in spamassassin/trunk: . build
> Log:
> Some code I had lying around since ages, maybe it will become useful one day. For now I dump it here to clean up my harddisk a bit ;~)
>
>
Just a pet peeve. That's not really a "Log" message. It should be
much more descriptive as to the code you are committing.
FYI: You can use svadmin to update the log message.
Michael
Re: svn commit: rev 46098 - in spamassassin/trunk: . build
Posted by Michael Parker <pa...@pobox.com>.
On Wed, Sep 15, 2004 at 03:31:26PM +0200, Malte S. Stretz wrote:
>
> You're right. Our log messages are often not very descriptive, we should
> really take the time to write one or two sentences about a commit.
>
It's too long to reproduce here, but I really like what the Subversion
folks have come up with, see section "Writing log messages:
http://svn.collab.net/repos/svn/trunk/HACKING
> > FYI: You can use svadmin to update the log message.
>
> I think svnadmin works only if you have direct access to the repository. I
> used the command 'svn propset svn:log --revprop -r 46098 -F /dev/stdin' to
> fix it.
>
Yeah, that's what I meant :)
Michael
Re: svn commit: rev 46098 - in spamassassin/trunk: . build
Posted by "Malte S. Stretz" <ms...@gmx.net>.
On Wednesday 15 September 2004 14:30 CET Michael Parker wrote:
> > Log:
> > Some code I had lying around since ages, maybe it will become useful
> > one day. For now I dump it here to clean up my harddisk a bit ;~)
>
> Just a pet peeve. That's not really a "Log" message. It should be
> much more descriptive as to the code you are committing.
You're right. Our log messages are often not very descriptive, we should
really take the time to write one or two sentences about a commit.
> FYI: You can use svadmin to update the log message.
I think svnadmin works only if you have direct access to the repository. I
used the command 'svn propset svn:log --revprop -r 46098 -F /dev/stdin' to
fix it.
Cheers,
Malte
--
[SGT] Simon G. Tatham: "How to Report Bugs Effectively"
<http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>
[ESR] Eric S. Raymond: "How To Ask Questions The Smart Way"
<http://www.catb.org/~esr/faqs/smart-questions.html>