Re: [PATCH] git-format-patch: add --no-binary to omit binary changes in the patch.

From: Jonas Fonseca <jonas.fonseca@gmail.com>
Date: May 9, 2008, 21:08 UTC
Message-ID: <2c6b72b30805091408i1924b755k3d1f5f4bb0cfaf08@mail.gmail.com>
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:

Show 18 quoted lines

> 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