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

Re: svn commit: propchange - r33150 - svn:log

From: Karl Fogel <kfogel_at_red-bean.com>
Date: Fri, 19 Sep 2008 13:32:11 -0400

Greg Stein <gstein_at_gmail.com> writes:
> Thanks, but I could change it myself if I was concerned. I'm worried
> about the pattern/trend rather than this specific case. Changing a log
> message occurred maybe once a month when I used to contribute. Now, I
> see a dozen a week. And many for what I would call "pedantic" reasons
> rather than helpful. CMike points out that log message fixed can be
> good for all future contributors/readers, but I think the rigidity is
> troublesome (as Lubbe noted).

Rigidity would be demanding that someone else comply in advance with a
nit-picky procedure.

But fixing typos in other people's log messages later? Whatever. If
someone wants to do that, let them (note: unrelated to the "tho" thing,
which was not a typo!). I don't do it myself, though I'll fix up
someone's log message before applying their patch, for example.

If these take some noticeable amount of time to review, then that's a
problem. But for me, the propchange emails just fly by: see it, nod,
then on to the next message. Virtually no time taken. If other people
really find them distracting, then okay, let's solve that. But I don't
see how it's a "rigidity" issue, if it's not imposed in advance.

Not knowing the specifics of Lübbe's case, I can't say whether there was
nit-picking going on there. Lübbe, if the project imposed procedures
that made you decide not to contribute, we need to know! On the other
hand, if you don't say what the specific problems were, there's not much
we can do to fix it...


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-09-19 19:32:27 CEST

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

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