Git development
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Andreas Ericsson <ae@op5.se>, Git Mailing List <git@vger.kernel.org>
Subject: Re: "mailinfo: Remove only one set of square brackets" considered harmful
Date: Wed, 15 Jul 2009 15:31:44 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.2.01.0907151520380.13838@localhost.localdomain> (raw)
In-Reply-To: <7vljmpegy4.fsf@alter.siamese.dyndns.org>



On Wed, 15 Jul 2009, Junio C Hamano wrote:
> 
> Even though it is silly not to rely on already well established
> conventions such as X-Mailing-List and List-ID but instead to waste
> precious real estate at the initial part of the Subject in this century
> merely for list identification purposes, this change regresses the end
> result.

Note that at least for the security list, it's not about "list 
identification", but simply to make the thing stand out in peoples 
mailboxes.

But I do agree that it's not perfect, and I would like to make the bracket 
removal stricter. Andreas' patch was a step in that direction. But 
different users would probably have different requirements.

For example, from a strictly git tools perspective, it's not even "any 
square bracket", and some people might want to remove only a single 
bracketed level, and only if it starts with "[PATCH".

For other uses, we want to remove the "Re: " at the beginning (and some 
crazy email readers use language/locale-specific versions like "Vs:" for 
that), and examples like the above "[Security]" from the security list.

So maybe the right solution is to allow people to configure this somehow.

		Linus

      parent reply	other threads:[~2009-07-15 22:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15 15:30 "mailinfo: Remove only one set of square brackets" considered harmful Linus Torvalds
2009-07-15 22:09 ` Junio C Hamano
2009-07-15 22:31   ` Junio C Hamano
2009-07-15 22:31   ` Linus Torvalds [this message]

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=alpine.LFD.2.01.0907151520380.13838@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --cc=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox