All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Carl Smedstad via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Carl Smedstad <carl.smedstad@protonmail.com>
Subject: Re: [PATCH] check-ignore: --non-matching without --verbose
Date: Mon, 23 May 2022 11:14:16 -0700	[thread overview]
Message-ID: <xmqqilpwru9z.fsf@gitster.g> (raw)
In-Reply-To: <pull.1236.git.1653310466062.gitgitgadget@gmail.com> (Carl Smedstad via GitGitGadget's message of "Mon, 23 May 2022 12:54:25 +0000")

"Carl Smedstad via GitGitGadget" <gitgitgadget@gmail.com> writes:

> The motivation for this is to use the underutilized invocation of
> --non-matching without --verbose to create a shorthand for what could be
> achieved by:

Not commenting on the patch itself, but ...

>
>     find . |
>       git check-ignore --verbose --non-matching |
>       grep $'^::\t' |
>       sed -e 's/.*\t//'

... feeding grep output to sed caught my eyes.  Isn't that equivalent to

	git ... |
	sed -n '/^::\t/s/.*\t//p'

?

  reply	other threads:[~2022-05-23 18:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 12:54 [PATCH] check-ignore: --non-matching without --verbose Carl Smedstad via GitGitGadget
2022-05-23 18:14 ` Junio C Hamano [this message]
2022-05-24 13:03   ` Carl Smedstad
2022-05-24 19:18     ` Junio C Hamano
2022-05-24 19:26       ` Ævar Arnfjörð Bjarmason
2022-05-23 20:44 ` Derrick Stolee
2022-05-24 13:06   ` Carl Smedstad
2022-05-24 13:01 ` [PATCH v2] " Carl Smedstad via GitGitGadget
2022-05-24 17:45 ` [PATCH] " 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=xmqqilpwru9z.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=carl.smedstad@protonmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.