mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <>
To: Todd Zullinger <>
Subject: Re: [PATCH] RelNotes: minor typo fixes in 2.15.1 draft
Date: Sun, 26 Nov 2017 12:49:08 +0900	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Todd Zullinger's message of "Sat, 25 Nov 2017 13:02:44 -0500")

Todd Zullinger <> writes:

> It was mildly surprising that the script didn't warn or complain about
> an unknown option.  After a quick look, that seems to be due to the
> Getopt::Long pass_through option which sends unknown options to
> format-patch.

Heh, that is another reason why I recommend against letting
send-email run format-patch from within (another a lot bigger one is
that running them seprately gives you a chance to look and proofread
the output from format-patch one more time before actually sending
them out, which also allows you to update additional comments after
the three-dash lines).

  reply	other threads:[~2017-11-26  3:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-25 17:33 [PATCH] RelNotes: minor typo fixes in 2.15.1 draft Todd Zullinger
2017-11-25 18:02 ` Todd Zullinger
2017-11-26  3:49   ` Junio C Hamano [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-11-25 17:32 Todd Zullinger

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 read-only IMAP folder(s) and NNTP newsgroup(s).