From: "Sverre Rabbelier" <alturin@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Miklos Vajna" <vmiklos@frugalware.org>, git@vger.kernel.org
Subject: Re: [RFC] Stopping those fat "What's cooking in git.git" threads
Date: Mon, 21 Jul 2008 01:19:37 +0200 [thread overview]
Message-ID: <bd6139dc0807201619g6c268488kd6b45109a246638d@mail.gmail.com> (raw)
In-Reply-To: <7v3am42lk2.fsf@gitster.siamese.dyndns.org>
On Mon, Jul 21, 2008 at 1:16 AM, Junio C Hamano <gitster@pobox.com> wrote:
>> On Sun, Jul 20, 2008 at 11:05 PM, Junio C Hamano <gitster@pobox.com> wrote:
>>> I could make "What's cooking" not a follow-up to the previous issue, or
>>> perhaps add "(volume 1.6.0, issue 28)" at the end of the Subject.
>>
>> The downside of this is that it'll be less easy to see the difference
>> with the previous version.
>
> My vague recollection is that it was Pasky who complained long time ago
> when "What's in" was not a follow-up to its previous round, which led me
> to switch my workflow to send them in the current form. You cannot
> satisfy certain people no matter what you do.
Add an interdiff at the bottom of the mail? You can't satisfy
everybody no matter what you do, but you can come quite far, it
usually means you have to do a lot of work to do so though.
next prev parent reply other threads:[~2008-07-20 23:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 20:51 [RFC] Stopping those fat "What's cooking in git.git" threads Miklos Vajna
2008-07-20 20:58 ` Stephan Beyer
2008-07-20 21:05 ` Junio C Hamano
2008-07-20 21:21 ` Miklos Vajna
2008-07-20 21:38 ` Jakub Narebski
2008-07-20 21:46 ` Stephan Beyer
2008-07-20 21:48 ` Petr Baudis
2008-07-20 22:50 ` Sverre Rabbelier
2008-07-20 23:16 ` Junio C Hamano
2008-07-20 23:19 ` Sverre Rabbelier [this message]
2008-07-21 4:24 ` Junio C Hamano
2008-07-21 5:27 ` Andreas Ericsson
2008-07-21 10:19 ` Johannes Schindelin
2008-07-21 6:33 ` Pierre Habouzit
2008-07-21 10:21 ` Johannes Schindelin
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=bd6139dc0807201619g6c268488kd6b45109a246638d@mail.gmail.com \
--to=alturin@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sverre@rabbelier.nl \
--cc=vmiklos@frugalware.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).