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

Re: Support for contributed properties and groups

From: Brock Janiczak <brockj_eclipse_at_ihug.com.au>
Date: 2004-11-21 08:36:01 CET

Ok, i have finally got a chance to read the bugtraq integration document.

It just sounds like an overly fancy way of populating the commit message
(for this one case only). Sort of like a pluggable commit dialog, but
with no *real* bug tracker integration. For instance, you can't
automatically resolve the issue post commit, or add a comment to the bug.

A simpler solution would have been to provide a customizable commit
template. CVS does this using an rcsinfo file on the server. Of
course, this would require a change to SVN itself, but it would be a
generally useful thing to have (not just for bug tracking). You
wouldn't have to retrieve the template each time you check out. It
could be copied into the admin area when the checkout is performed (like
CVS). Also, if you are going to be checking in, chances are you have a
network connection available. Another cople of byte isn't going to kill
anyone (compared to transmitting file contents).

Does anyone other than Tortiose support these properties at the moment?
Most importantly, does the standard command line client support them?
By the way, I am in no way suggesting that we *shouldn't* support them.

Mark Phippard wrote:

>The configuration of the integration is based on properties. What I meant
>was that the bug ID itself is not stored as a property. So you cannot
>solve this problem by making property management fancier.

I never intended to make property management 'fancier'. I merely wanted
a way to be able to present the user with a list (or tree) of registered
properties to aviod typos and to hint what each proeprty is for. If a
user wished to create a user defined proeprty for recording the last bug
number that affected the file, they can do that. Recording the bug
number a change was for could be useful, as it means you don't have to
parse the commit message to find it (remember properties are versioned
too). Obviously, the user should also be able to enter an
'unregistered' properties too, they just don't get any meta information
explaining what the property is for or any type checking, as is
currently done.

Received on Sun Nov 21 18:36:01 2004

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