git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Beller <sbeller@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] diff: document diff-filter exclusion
Date: Thu, 14 Jul 2016 12:27:10 -0700	[thread overview]
Message-ID: <CAGZ79ka5ZB=vL3j0Zm3vAvdZi7jA1gPAs61NhkVABZepfcuLvw@mail.gmail.com> (raw)
In-Reply-To: <xmqq7fcoqb5a.fsf@gitster.mtv.corp.google.com>

On Thu, Jul 14, 2016 at 12:20 PM, Junio C Hamano <gitster@pobox.com> wrote:
> In v1.8.5 days, 7f2ea5f0 (diff: allow lowercase letter to specify
> what change class to exclude, 2013-07-17) taught the "--diff-filter"
> mechanism to take lowercase letters as exclusion, but we forgot to
> document it.
>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
>  Documentation/diff-options.txt | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/diff-options.txt b/Documentation/diff-options.txt
> index 3ad6404..073c7e5 100644
> --- a/Documentation/diff-options.txt
> +++ b/Documentation/diff-options.txt
> @@ -399,6 +399,9 @@ ifndef::git-format-patch[]
>         paths are selected if there is any file that matches
>         other criteria in the comparison; if there is no file
>         that matches other criteria, nothing is selected.
> ++
> +Also, these upper-case letters can be downcased to exclude.  E.g.
> +`--diff-filter=ad` excludes added and deleted paths.
>

This looks good for the neighboring thread. :)
http://thread.gmane.org/gmane.comp.version-control.git/299512

      reply	other threads:[~2016-07-14 19:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-14 19:20 [PATCH] diff: document diff-filter exclusion Junio C Hamano
2016-07-14 19:27 ` Stefan Beller [this message]

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='CAGZ79ka5ZB=vL3j0Zm3vAvdZi7jA1gPAs61NhkVABZepfcuLvw@mail.gmail.com' \
    --to=sbeller@google.com \
    --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).