[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

re: Log message templates

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2004-07-27 21:44:46 CEST

Greg Hudson <ghudson@MIT.EDU> wrote on 07/27/2004 03:37:43 PM:

> On Tue, 2004-07-27 at 14:15, Mark Phippard wrote:
> > Does anyone think this would ever make a good Subversion feature?
> > everyone use some kind of bug tracking system these days? Why not
make it
> > a full-fledged part of the UI?
> Not everyone uses a bug-tracking system, and those who do don't
> necessarily want integration with their version control systems. We
> need to be careful to make sure that our features are about version
> control, or we wander into a different product space which isn't as
> popular.

I figured that would be the response, and do not disagree, but if the
validation were configurable and the default was to not require the
property, I think it could be a good enhancement. In my personal opinion,
I think an issue ID is just as relevant as a log message. We would rather
have our people write their notes in the issue system and I see this as
two sides of the same coin. I think this would be a good area for svn to
distinguish itself from the field and it could make it easier for those of
us with issue tracking systems to integrate in a better manner.

> On the other hand, I've long felt that it would be a good idea to be
> able to set arbitrary rev-props in a commit. If we had a good syntax
> for that, it would be almost as convenient as your proposed -id flag.

That sounds pretty good to me. I really didn't think that even --id would
be acceptable because it seems like it would be confused with the $Id$
keyword. I just do not like --bug and wanted to keep the example generic.
> (Incidentally, we would never have an option like -id. Our option
> parser would treat that as equivalent to -i -d. Multi-character option
> names are preceded by two dashes.)

I always wondered about why sometimes it was two dashes. That makes


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 27 21:44:53 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.