From: Linus Torvalds <torvalds@osdl.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Junio C Hamano <junkio@cox.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: git-applymbox broken?
Date: Mon, 12 Jun 2006 12:10:27 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0606121204220.5498@g5.osdl.org> (raw)
In-Reply-To: <m13bea6w13.fsf@ebiederm.dsl.xmission.com>
On Mon, 12 Jun 2006, Eric W. Biederman wrote:
>
> Below is an example of the kind of patch that inspired me to relax the
> rules on parsing in body headers (this comes from Andi Kleen quilt tree).
And this is wrong.
We should _not_ accept crappy patches, and then start guessing at what the
person meant.
>From the very beginning of git, I tried to make it extremely clear that
there is never any guessing going on. We don't use "heuristics" except as
a pure optimization: ie a heuristic can have a _performance_ impact, but
it must never EVER have semantic impact.
SCM's are not about guessing. They are about saving the _exact_ state that
the user asked for. No "let's try to be nice", no gray areas.
If the new git-applymbox just takes random lines from the body of the
email, and decides that they may be authorship information, then that is a
BUG. The "From: " line in the middle of an email may well be about
somebody having _discovered_ the bug, and we're quoting him as part of the
explanation. It does NOT mean that it's about authorship.
So we should ONLY check for "From:" (and perhaps "Subject:" and "Date:")
at the very top of the email body. NOWHERE ELSE.
The fact that somebody has a crappy quilt tree, and the fact that quilt is
very much a "anything goes" kind of laissez faire system does not mean,
and should NEVER mean that git becomes the same kind of mess of "let's do
a best effort and try to guess what somebody means" kind of thing.
I check and edit my emails before I apply them, and I try to teach the
people who send them manners and what the rules are. THAT is the way to
handle this, not by having the tool itself become unreliable and random
Linus
next prev parent reply other threads:[~2006-06-12 19:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-11 22:40 git-applymbox broken? Linus Torvalds
2006-06-11 23:33 ` Eric W. Biederman
2006-06-12 0:37 ` Linus Torvalds
2006-06-12 7:35 ` Eric W. Biederman
2006-06-12 18:45 ` [PATCH] Ignore blank lines among this inbody headers Eric W. Biederman
2006-06-12 19:29 ` Eric W. Biederman
2006-06-12 18:58 ` git-applymbox broken? Eric W. Biederman
2006-06-12 19:10 ` Linus Torvalds [this message]
2006-06-12 19:48 ` [PATCH] Don't parse any headers in the real body of an email message Eric W. Biederman
2006-06-12 20:10 ` git-applymbox broken? Eric W. Biederman
2006-06-12 22:43 ` Johannes Schindelin
2006-06-12 23:54 ` Randy.Dunlap
2006-06-13 3:41 ` Ryan Anderson
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=Pine.LNX.4.64.0606121204220.5498@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=ebiederm@xmission.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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;
as well as URLs for NNTP newsgroup(s).