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

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

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

From: Miklos Vajna <hidden>
Date: 2016-06-15 22:44:58

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.

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

From: Stephan Beyer <hidden>
Date: 2016-06-15 22:44:58

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 [off-list ref], PGP 0x6EDDD207FCC5040F
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help