From: Philip Hofstetter <phofstetter@sensational.ch>
To: "Lukas Sandström" <luksan@gmail.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [PATCH] git am/mailinfo: Don't look at in-body headers when rebasing
Date: Thu, 19 Nov 2009 00:47:15 +0100 [thread overview]
Message-ID: <aa2993680911181547p4cbbf12cq74b482f63e59d007@mail.gmail.com> (raw)
In-Reply-To: <4B0478ED.30306@gmail.com>
Hi,
On Wed, Nov 18, 2009 at 11:45 PM, Lukas Sandström <luksan@gmail.com> wrote:
> The actual change is that mailinfo doesn't look for in-body headers
> at all if --no-inbody-headers is passed. git-am now passes this option
> to mailinfo when rebasing.
after all the earlier discussion and a lot of thinking, I have to say,
that IMHO, this is the best option as it doesn't rely on heuristics
and now that you chose a descriptive command line switch, even the
small problem of "why exactly is this switch here?" seems to go away.
As I have no experience in git's codebase at all, I'll leave the
commenting on the patch itself to the people with clue, but
conceptionally, this feels much better than the method 1
> This won't handle the case when a "bad" patch is passed to git-am from
> somewhere else than git rebase.
of course, that leaves the question what "somewhere else" can contain.
If it's just manual calls to git-am, this is a non-issue as it's
easily fixed by the caller. If it's being called from other
higher-level operations though, you might run into the same issue
again.
Here too, I can't really provide any meaningful input though as I just
don't know well enough what really makes git tick.
Just my two cents :-)
Philip
next prev parent reply other threads:[~2009-11-18 23:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 14:20 git-mailinfo doesn't stop parsing at the end of the header Philip Hofstetter
2009-11-18 15:51 ` Jeff King
2009-11-18 16:42 ` Jeff King
2009-11-18 22:45 ` [PATCH] git am/mailinfo: Don't look at in-body headers when rebasing Lukas Sandström
2009-11-18 23:47 ` Philip Hofstetter [this message]
2009-11-19 8:51 ` [PATCH v2] " Lukas Sandström
2009-11-19 15:36 ` Jeff King
2009-11-20 16:12 ` [PATCH] " Lukas Sandström
2009-11-18 17:11 ` git-mailinfo doesn't stop parsing at the end of the header Philip Hofstetter
2009-11-18 17:24 ` Jeff King
2009-11-18 17:46 ` Jakub Narebski
2009-11-18 18:42 ` Jeff King
2009-11-18 19:57 ` Philip Hofstetter
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=aa2993680911181547p4cbbf12cq74b482f63e59d007@mail.gmail.com \
--to=phofstetter@sensational.ch \
--cc=git@vger.kernel.org \
--cc=luksan@gmail.com \
--cc=peff@peff.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).