>> My point was that the overwhelming majority of those TSVN users you
>> describe would never run into this parm, the ones that do would be ones
>> where someone decided they needed it. In those scenarios, I believe that
> Not really. There are many users who would want such a list of open
> issues, but just as a help, _not_ to enforce a bug-ID. By enforcing it
> we would anger those users a lot, because they either can't use that
> feature or would be forced to use bogus ID's to commit certain changes.
I totally second that... it should _ imho _ the role of the SVN
client. The only secure way to implement that is in my opinion a
server side pre-commit hook.
On the other hand, I really think that the issues list would be a
great asset for TSVN. Of course, you can always fire up your browser,
look for the issue, and so on, but being able to browse them from the
SVN client can really be a time saver. And of course you can still
start your browser if you need more advanced bug filtering...
Steve is totally right about avoiding useless complexity in such a
feature. TSVN has managed to remain simple (from a frontend point of
vue), and it has to stay on the simplicity & ergonomy road, imho.
Just my 0.02 EUR...
Katana mailto:katana@katana-inc.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Oct 27 23:27:54 2004