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

Re: [Issue 2367] get rid of "... | N lines" slot in log message header

From: <kfogel_at_collab.net>
Date: 2005-07-20 20:39:17 CEST

Greg Hudson <ghudson@MIT.EDU> writes:
> On Wed, 2005-07-20 at 11:08 -0500, kfogel@collab.net wrote:
> > There has been no list discussion, until now.
> Why did you open an issue with no list discussion?

When we started asking people to do list discussion first, it was
aimed at new users who would file non-bugs or bring up topics that had
been discussed to death already. The point was to avoid the overhead
of explaining that to them in the issue tracker, since it's easier to
explain that on the list. I already knew that this issue had not been
discussed before, so that concern did not apply. Another way to say
it is that I "consulted" a committer who knew the relevant history,
and that committer was me. Experienced developers file issues all the
time without prior discussion, when they're pretty sure it's for a
good reason, and we haven't objected to this practice. (See similar
issue #2366, for example.)

However, with #2267, my judgement was off: I should have realized this
had the potential to be controversial, and brought it up on the list
first. There are so many issues flying around in that tracker that
it's worth minimizing the number of new filings by any means
available. Sorry about that.

> (I'm also not terribly fond of the idea. When feasible, software should
> work all the time, not just in the common cases.)

What sticks in my craw is the tendency to misunderstand the current
syntax. However, it's not a big deal; if I'm not persuading you and
Maxb, then I think consensus is unlikely and I'll close the issue.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 20 21:30:36 2005

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.