From: Miklos Vajna <vmiklos@frugalware.org>
To: git@vger.kernel.org
Subject: [RFC] Stopping those fat "What's cooking in git.git" threads
Date: Sun, 20 Jul 2008 22:51:25 +0200 [thread overview]
Message-ID: <20080720205125.GP10347@genesis.frugalware.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
Hi,
As far as I remember, it was Petr Baudis who first asked on IRC if
these threads (being so big and deep) are annoying for other people as
well or not.
I think it's just hard to follow the discussion as the subject is
usually not changed, so for example when the subject contains "merge", I
carefully read that mail, but I can easily miss such a mail if it's
still "What's cooking in".
An other problem with deep threads is that it just doesn't fit in one's
screen, so I had to use tricks for example to see if a mail was a reply
to my mail or to some other mail.
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.
Thanks.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-07-20 20:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 20:51 Miklos Vajna [this message]
2008-07-20 20:58 ` [RFC] Stopping those fat "What's cooking in git.git" threads 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
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=20080720205125.GP10347@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--cc=git@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 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.