From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephan Beyer Subject: Re: [RFC] Stopping those fat "What's cooking in git.git" threads Date: Sun, 20 Jul 2008 22:58:52 +0200 Message-ID: <20080720205852.GA5950@leksak.fem-net> References: <20080720205125.GP10347@genesis.frugalware.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0F1p//8PRICkK4MW" Cc: git@vger.kernel.org To: Miklos Vajna X-From: git-owner@vger.kernel.org Sun Jul 20 23:02:42 2008 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1KKg3E-0001Ht-02 for gcvg-git-2@gmane.org; Sun, 20 Jul 2008 23:02:40 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752443AbYGTU65 (ORCPT ); Sun, 20 Jul 2008 16:58:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752459AbYGTU65 (ORCPT ); Sun, 20 Jul 2008 16:58:57 -0400 Received: from mail.gmx.net ([213.165.64.20]:45332 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752365AbYGTU64 (ORCPT ); Sun, 20 Jul 2008 16:58:56 -0400 Received: (qmail invoked by alias); 20 Jul 2008 20:58:54 -0000 Received: from q137.fem.tu-ilmenau.de (EHLO leksak.fem-net) [141.24.46.137] by mail.gmx.net (mp028) with SMTP; 20 Jul 2008 22:58:54 +0200 X-Authenticated: #1499303 X-Provags-ID: V01U2FsdGVkX1+d2Ix8xYydLHgq5a2sTe/kTyV/YO04NOE+BqYq5F iyPOaEZ1EmOCOe Received: from sbeyer by leksak.fem-net with local (Exim 4.69) (envelope-from ) id 1KKfzY-0003Z6-FK; Sun, 20 Jul 2008 22:58:52 +0200 Content-Disposition: inline In-Reply-To: <20080720205125.GP10347@genesis.frugalware.org> X-Y-GMX-Trusted: 0 X-FuHaFi: 0.67 Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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: )") 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 --=20 Stephan Beyer , PGP 0x6EDDD207FCC5040F --0F1p//8PRICkK4MW Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFIg6cMbt3SB/zFBA8RAnliAKCPh/GCTBH2MnL3yHDE+avnV2vvGQCdFcec uSX+bfJNzBJ+Qxdf059aTPc= =s8e3 -----END PGP SIGNATURE----- --0F1p//8PRICkK4MW--