C. Michael Pilato wrote:
> Greg Hudson <ghudson@MIT.EDU> writes:
>
>>I've seen about a half dozen requests for log message templates, a
>>feature CVS has which we don't. Does anyone object if I file an
>>enhancement issue for them?
>
> Sure. Maybe make that issue depend on the solution to
> "server-dictated configuration options", since that's the way CVS does
> its commit templates. Had we a generic mechanism for sending config
> stuffs from server to client, this would be low-hanging fruit.
Oh yes! Server-dictated config options is exactly what I would need
right now:
I was contacted by some guys who want to make TSVN integrate into their
bugtracking software. But whatever idea we come up with ends in the
missing feature of server-dictated config options:
- Adding the bug-ID/Issue-Number to the log message in a format so that
the bugtracker can parse it. Since each project can have a different
bugtracker this format should be stored somehow in a server config.
- Add the bug-ID/Issue-number as a special property to each file of a
commit (before the actual commit). The format of that property could
simply be the bug-ID/Issue-number, but I'd like it better configurable
per project.
- Starting the browser with the bug-ID(s) stored in the property of a
file and the bugtracker-URL. To prevent having the user enter the
bugtracker-URL of each project manually this should be stored on the
server too.
So you can see: all these informations/options should best be stored on
a per-project basis, and that would require server-dictated config options.
Just some thought for what this would be useful for too.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 27 18:04:57 2004