Re: [RFC] Stopping those fat "What's cooking in git.git" threads

[Stephan Beyer <s-beyer@gmx.net>]

[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]

Hi,

Miklos Vajna wrote:
> 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".

I agree that changing a subject (with "(was: <oldsubject>)") is nicer to
find specific mails later.

> 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?

"Everyone should" bla usually does not work in open communities.

And why not vice versa?
A new "What's cooking in " mail with new cookings could start a new
thread instead of replying to old "What's cooking in" mails...

> If those large threads just annoys a few people and most people are
> happy with the current situation then sorry for the noise.

Hm, I don't really care.

Mutt is able to link and break threads with

	#       break-thread         break the thread in two
	&        link-threads         link tagged message to the current one

so I am able to design the threads as I like it ;)
(And I am also able to change subjects as I like, so I don't have a
problem.)

Regards,
  Stephan

-- 
Stephan Beyer <s-beyer@gmx.net>, PGP 0x6EDDD207FCC5040F

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]