From: Michael J Gruber <michaeljgruber+gmane@fastmail.fm>
To: Junio C Hamano <gitster@pobox.com>
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 18:29:29 +0200 [thread overview]
Message-ID: <48C6A469.30702@fastmail.fm> (raw)
In-Reply-To: <7vtzcp71el.fsf@gitster.siamese.dyndns.org>
Junio C Hamano venit, vidit, dixit 09.09.2008 18:02:
> 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.
For many projects, things become unstable after a major release. This is
the time to experiment. Right before a major release, everything needs
to settle down, with a focus on bugfixes and stability.
That said, I know the "logic" of the make targets now, so I really don't
care any more what they are named. I just meant to keep others from
being confused. So I guess I'll go with the existing naming and fit
quick-install-html right in. Will go into a new thread tomorrow or so.
> 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 ;-).
Junio,
I think you handled that in the best possible way, and I felt
sympathetic with you when that thread with a RFC went OT back to
discussing things over again.
Cheers,
Michael
prev parent reply other threads:[~2008-09-09 16:30 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
2008-09-09 16:29 ` Michael J Gruber [this message]
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=48C6A469.30702@fastmail.fm \
--to=michaeljgruber+gmane@fastmail.fm \
--cc=bert.wesarg@googlemail.com \
--cc=brandon@ifup.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=guilt@lists.josefsipek.net \
--cc=jeffpc@josefsipek.net \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).