git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git list <git@vger.kernel.org>, Adam Spiers <git@adamspiers.org>
Subject: Re: [PATCH 2/2] format-patch: --inline-single
Date: Fri, 22 Feb 2013 12:23:53 -0500	[thread overview]
Message-ID: <20130222172353.GA17475@sigill.intra.peff.net> (raw)
In-Reply-To: <7vmwuws3bo.fsf@alter.siamese.dyndns.org>

On Fri, Feb 22, 2013 at 08:47:39AM -0800, Junio C Hamano wrote:

> Jeff King <peff@peff.net> writes:
> 
> >> ... <helper function to see if the user is the author> ...
> >> +}
> >
> > Nice, I'm glad you handled this case properly. I've wondered if we
> > should have an option to do a similar test when writing out the "real"
> > message format. I.e., to put the extra "From" line in the body of the
> > message when !is_current_user(). Traditionally we have just said "that
> > is the responsibility of the MUA you use", and let send-email handle it.
> > But it means people who do not use send-email have to reimplement the
> > feature themselves.
> 
> I am not sure if I follow.  Do you mean that you have to remove
> fewer lines if you omit Date/From when it is from you in the first
> place?

Sorry, I think I confused you by going off on a tangent. The rest of my
email was about dropping unnecessary lines from the inline view.  But
here I was talking about another possible use of the "is user the
author" function. For the existing view, we show:

  From: A U Thor <author@example.com>
  Date: ...
  Subject: [PATCH] whatever

  body

and if committer != author, we expect the MUA to convert that to:

  From: C O Mitter <committer@example.com>
  Date: ...
  Subject: [PATCH] whatever

  From: A U Thor <author@example.com>

  body

That logic happens in git-send-email right now, but given that your
patch adds the "are we the author?" function, it would be trivial to add
a "--sender-is-committer" option to format-patch to have it do it
automatically. That saves the MUA from having to worry about it.

> People who do not use send-email (like me) slurp the output
> 0001-have-gostak-distim-doshes.patch into their MUA editor, tell the
> MUA to use the contents on the Subject: line as the subject, and
> remove what is redundant, including the Subject.  Because the output
> cannot be used as-is anyway, I do not think it is such a big deal.

That is one way to do it. Another way is to hand the output of
format-patch to your MUA as a template, making it a starting point for a
message we are about to send. No manual editing is necessary in that
case, unless the "From" header does not match the sender identity.

> And those who have a custom mechanism to stuff our output in their
> MUA's outbox, similar to what imap-send does, would already have to
> have a trivial parser to read the first part of our output up to the
> first blank line (i.e. parsing out the header part) and formatting
> the information it finds into a form that is understood by their
> MUA.

Not necessarily. The existing format is an rfc822 message, which mailers
understand already. It's perfectly cromulent to do:

  git format-patch --stdout "$@" >mbox &&
  mutt -f mbox

and use mutt's "resend-message" as a starting point for sending each
message. No editing is necessary except for adding recipients (which you
can also do on the command-line to format-patch).

> Omitting From: or Date: lines would not help those people who
> already have established the procedure to handle the "Oh, this one
> is from me" case, or to send the output always with the Sender: and
> keeping the From: intact.  So,...

Right, my point was to help people who _should_ have implemented the
"oh, this one is from me" case, but were too lazy to do so (and it's
actually a little tricky to get right, because you might have to adjust
the mime headers to account for encoded author names).

-Peff

  reply	other threads:[~2013-02-22 17:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-19  5:24 [BUG] git-check-ignore: Segmentation fault Zoltan Klinger
2013-02-19 13:40 ` Adam Spiers
2013-02-19 14:06   ` [PATCH 1/2] t0008: document test_expect_success_multi Adam Spiers
2013-02-19 14:06     ` [PATCH 2/2] check-ignore.c: fix segfault with '.' argument from repo root Adam Spiers
2013-02-19 17:54       ` Junio C Hamano
2013-02-19 19:07         ` Adam Spiers
2013-02-19 19:21           ` [PATCH v2 2/2] check-ignore.c, dir.c: " Adam Spiers
2013-02-19 19:59             ` Junio C Hamano
2013-02-19 22:03               ` Junio C Hamano
2013-02-20  1:57                 ` Adam Spiers
2013-02-20  2:47                   ` Junio C Hamano
2013-02-20 12:43                     ` Adam Spiers
2013-02-20  1:30               ` Adam Spiers
2013-02-19 19:56           ` Re* [PATCH 2/2] check-ignore.c: " Junio C Hamano
2013-02-20  2:00             ` Adam Spiers
2013-02-20  2:53               ` Junio C Hamano
2013-02-20 10:47                 ` Adam Spiers
2013-02-21 20:15                   ` Junio C Hamano
2013-02-21 20:17                     ` [PATCH 1/2] format-patch: rename "no_inline" field Junio C Hamano
2013-02-21 20:26                     ` [PATCH 2/2] format-patch: --inline-single Junio C Hamano
2013-02-21 23:13                       ` Jeff King
2013-02-21 23:41                         ` Junio C Hamano
2013-02-21 23:47                           ` Junio C Hamano
2013-02-22 15:32                         ` Adam Spiers
2013-02-22 16:47                         ` Junio C Hamano
2013-02-22 17:23                           ` Jeff King [this message]
2013-02-19 17:37     ` [PATCH 1/2] t0008: document test_expect_success_multi Junio C Hamano

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=20130222172353.GA17475@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@adamspiers.org \
    --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;
as well as URLs for NNTP newsgroup(s).