All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Michael J Gruber <michaeljgruber+gmane@fastmail.fm>
Cc: Bert Wesarg <bert.wesarg@googlemail.com>,
	"Josef 'Jeff' Sipek" <jeffpc@josefsipek.net>,
	Git Mailing List <git@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	guilt@lists.josefsipek.net, Brandon Philips <brandon@ifup.org>
Subject: Re: [ANNOUNCE] Guilt v0.31
Date: Tue, 09 Sep 2008 09:02:42 -0700	[thread overview]
Message-ID: <7vtzcp71el.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <48C698DF.7010401@fastmail.fm> (Michael J. Gruber's message of "Tue, 09 Sep 2008 17:40:15 +0200")

Michael J Gruber <michaeljgruber+gmane@fastmail.fm> writes:

> I keep hearing this argument, and I'm even more surprised to hear it
> right after a major release. If not now then when's a good time for
> cleaning up confusing inconsistencies?

Actually, after a major release is the worst time to push for such an
agenda.

Especially when that release burned the maintainer with numerous complains
against a major change in it, that has been advertised for a long time,
which was pushed by other people for no good reason other than "such a
clean-up would make things much tidier".

Grrr ;-).




  reply	other threads:[~2008-09-09 16:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08 13:52 [ANNOUNCE] Guilt v0.31 Josef 'Jeff' Sipek
2008-09-08 15:39 ` Michael J Gruber
2008-09-08 15:45   ` Josef 'Jeff' Sipek
2008-09-08 15:58   ` Josef 'Jeff' Sipek
2008-09-08 18:33 ` Bert Wesarg
2008-09-08 18:43   ` Josef 'Jeff' Sipek
2008-09-08 18:50     ` Bert Wesarg
2008-09-08 19:17       ` Junio C Hamano
2008-09-09 10:10         ` Michael J Gruber
2008-09-09 13:02           ` Michael J Gruber
2008-09-09 15:13             ` Junio C Hamano
2008-09-09 15:40               ` Michael J Gruber
2008-09-09 16:02                 ` Junio C Hamano [this message]
2008-09-09 16:29                   ` Michael J Gruber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vtzcp71el.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=bert.wesarg@googlemail.com \
    --cc=brandon@ifup.org \
    --cc=git@vger.kernel.org \
    --cc=guilt@lists.josefsipek.net \
    --cc=jeffpc@josefsipek.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michaeljgruber+gmane@fastmail.fm \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.