Re: [RFC] Stopping those fat "What's cooking in git.git" threads
- From
Petr Baudis <pasky@suse.cz>
- Date
- Jul 20, 2008, 21:48 UTC
- Message-ID
- <20080720214811.GF32184@machine.or.cz>
- In-Reply-To
- <7vsku44679.fsf@gitster.siamese.dyndns.org>
On Sun, Jul 20, 2008 at 02:05:30PM -0700, Junio C Hamano 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.
Show 5 quoted lines
> 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?
I think responses to the what's cooking mails per se should certainly have in-reply-to set properly. I'm rather wondering if there's some specific reasons why do you keep all the "What's cooking" mails in a single thread? If there is nothing particular, keeping each "What's cooking" report in a separate mail might be easier on a portion of readers. I will use break-thread now (thanks, didn't know about it!) but the practice seems strange to me.
-- Petr "Pasky" Baudis As in certain cults it is possible to kill a process if you know its true name. -- Ken Thompson and Dennis M. Ritchie