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

Re: [TSVN] Re: Integration with bug tracking tools

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2004-08-22 02:36:03 CEST

> I won't add such a property unless you pay for my bodyguard. Because if
> I add that I will need a bodyguard protecting me from very angry users!
> To make that clear I wrote in the document mentioned in the first mail
> that an empty text box (i.e. if the user doesn't write any issue number
> in it) means that _no error_ is given by the client. It is then assumed
> that the commit doesn't apply to any issues.

OK, I don't get it. All I am suggesting is that there be a setting,
default would be off. If you would never use it, don't. I probably
wouldn't either. I can see where some people would like to have it so that
they did not have to deal with fixing log messages after the fact. Sure,
they could add a pre-commit hook, but it would be a lot harder to write
than it would be to add the feature, and if the feature is just in the GUI
clients, a user can always use the command line to get by it.

My larger point, is why impose your point of view on others. That seems to
be what you are trying not to do in one sense, but in fact that is what you
are actually doing. The property would be off by default, someone would
have to configure it to turn it on, why should you care? Who says you are
right?

Not to beat this to death, but think of an admin in control of a repository
with hundreds of programmers. The admin can use the command line to do
stuff like create branches and tags that do not require bug ID's. They
want their programmers to always supply one though. If you have hundreds
of programmers you are going to constantly be fixing log messages for them,
not to mention writing scripts to inspect the database to see if there are
commits with no bug ID. Although I suppose if you had a post-commit email
script you could just keep track of the commits via email. The point is
that programmers can have something they enter that means it does not have
a specific issue number, if that is an issue, or someone can just not use
the feature. Why not just try to support more usage models? Finally, as
that other poster pointed out a few days ago, there might be admins that
want absolutely everything to have a bug ID associated with it, even basic
repository admin tasks.

Thanks

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sun Aug 22 13:23:20 2004

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

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