git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jonas Fonseca" <jonas.fonseca@gmail.com>
To: "Caio Marcelo de Oliveira Filho" <cmarcelo@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-format-patch: add --no-binary to omit binary changes in the patch.
Date: Fri, 9 May 2008 23:08:18 +0200	[thread overview]
Message-ID: <2c6b72b30805091408i1924b755k3d1f5f4bb0cfaf08@mail.gmail.com> (raw)
In-Reply-To: <1210096079-32399-1-git-send-email-cmarcelo@gmail.com>

On Tue, May 6, 2008 at 7:47 PM, Caio Marcelo de Oliveira Filho
<cmarcelo@gmail.com> wrote:
> diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt
> index b5207b7..81c930a 100644
> --- a/Documentation/git-format-patch.txt
> +++ b/Documentation/git-format-patch.txt
> @@ -150,6 +150,12 @@ include::diff-options.txt[]
>        Instead of using `.patch` as the suffix for generated
>        filenames, use specified suffix.  A common alternative is
>        `--suffix=.txt`.
> +
> +--no-binary::
> +       Don't output contents of changes in binary files, just take note
> +       that they differ.  Note that this disable the patch to be properly
> +       applied.  By default the contents of changes in those files are
> +       encoded in the patch.
>  +
>  Note that you would need to include the leading dot `.` if you
>  want a filename like `0001-description-of-my-change.patch`, and
> diff --git a/builtin-log.c b/builtin-log.c

The '+' on the start of a line means continue last list item. In other
words, your update to the manpage will result in the --no-binary
option having a second paragraph that was really intended for the
--suffix option.

-- 
Jonas Fonseca

  parent reply	other threads:[~2008-05-09 21:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-06 17:47 [PATCH] git-format-patch: add --no-binary to omit binary changes in the patch Caio Marcelo de Oliveira Filho
2008-05-09 17:24 ` Robin Rosenberg
2008-05-09 21:08 ` Jonas Fonseca [this message]
2008-05-09 22:55   ` Caio Marcelo de Oliveira Filho

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=2c6b72b30805091408i1924b755k3d1f5f4bb0cfaf08@mail.gmail.com \
    --to=jonas.fonseca@gmail.com \
    --cc=cmarcelo@gmail.com \
    --cc=git@vger.kernel.org \
    /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).