On 8/29/06, Paul Benedict <[EMAIL PROTECTED]> wrote:
I never tried changing the log message and I don't know if I should :-) The message is exactly what I intended to be: completes the ticket. I don't want to touch multiple projects under this ticket; I will open up one for taglib and one for the examples app. But because you feel strongly I should include a message, I will include a description in the future even if it is the same as the ticket title.
The way I look at it is that if I am looking through the SVN logs to see when a particular change happened (and not specifically for when a particular issue was resolved), it's really quite annoying to find log entries that have nothing but an issue number in them. It tells me nothing, and now I have to go off to JIRA to find out what that was all about. Adding a brief description along with the issue number allows me to quickly get an idea of what might have happened in a particular commit without leaving the tool that I'm in each time I look at a new revision entry. My 2 cents. -- Martin Cooper -- Paul
Wendy Smoak wrote: > On 8/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> Author: pbenedict >> Date: Mon Aug 28 21:26:25 2006 >> New Revision: 437956 >> >> URL: http://svn.apache.org/viewvc?rev=437956&view=rev >> Log: >> STR-2864 >> > > This should have a description of the change in addition to the JIRA issue. > > ( I've never tried it, but it looks like Phil was successful at > changing a log message: > < http://www.nabble.com/Re%3A-svn-commit%3A-r432981----jakarta-commons-proper-dbcp-trunk-xdocs-configuration.xml-p5896866.html > > > which links to: http://subversion.tigris.org/faq.html#change-log-msg ) > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
