From: Junio C Hamano <gitster@pobox.com>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Stopping those fat "What's cooking in git.git" threads
Date: Sun, 20 Jul 2008 14:05:30 -0700 [thread overview]
Message-ID: <7vsku44679.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080720205125.GP10347@genesis.frugalware.org> (Miklos Vajna's message of "Sun, 20 Jul 2008 22:51:25 +0200")
Miklos Vajna <vmiklos@frugalware.org> writes:
> So here is what I thought about: What about if everyone (except Junio,
> of course) would change the subject _and_ remove the In-Reply-To: header
> when replying to those mails?
>
> If those large threads just annoys a few people and most people are
> happy with the current situation then sorry for the noise.
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.
But I think it is a good idea to change the subject when responding to one
part of the message to say which topic your response is about.
I do not know if stripping "In-reply-to" is a great idea, though. They
are responses, aren't they?
next prev parent reply other threads:[~2008-07-20 21:08 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 [this message]
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
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=7vsku44679.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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).