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

Re: Installing log-police.py in Subversion's repository.

From: Max Bowsher <maxb1_at_ukf.net>
Date: 2006-03-09 01:46:12 CET

Hash: SHA1

kfogel@collab.net wrote:
> Max Bowsher <maxb1@ukf.net> writes:
>> I vote -0.5 on this.
>> I feel that this issue is so irrelevant, the benefits provided so
>> negligible, that the additional possibilities for problems, and
>> additional administrator time, however small they may be, are not justified.
> Okay. I disagree, but it's largely a matter of taste and I can't
> really say anything that would make your -0.5 come down (uh, go up).
>> Additionally, I feel that deciding that it is useful enough to warrant
>> installation on our own repository is logically irreconcilable with a
>> decision to keep the functionality out of the Subversion core code.
> That I don't get. *Every* hook running in our repository implements
> something we decided not to put in core Subversion. I don't see how
> this one is any different. Deciding to enforce certain log message
> conventions for our project doesn't mean we think all other projects
> in the world should use them.
> In short: huh? :-)

Well, can't get much shorter than that! :-)

What I mean is:
As I understand it (possibly incorrectly), we haven't put this
functionality into core because we deem it to be of niche interest, and
not important for the majority of repositories.

Now, if we consider ourselves to be an example of a typical project
using Subversion source control (do we? I'd tend to assume we do), then
if we are interested in log canonicalization, that conflicts with the
supposition that log canonicalization is of niche interest.


Version: GnuPG v1.4.1 (Cygwin)


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Mar 9 01:46:31 2006

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