From: Junio C Hamano <gitster@pobox.com>
To: Brigham Campbell <me@brighamcampbell.com>
Cc: git@vger.kernel.org, Patrick Steinhardt <ps@pks.im>
Subject: Re: [PATCH] git-contacts: allow inputting patch via stdin
Date: Mon, 14 Sep 2026 21:29:21 -0700 [thread overview]
Message-ID: <xmqqbj9z2l3y.fsf@gitster.g> (raw)
In-Reply-To: <20260914-git-contacts-stdin-v1-1-9ac628e6fd20@brighamcampbell.com> (Brigham Campbell's message of "Mon, 14 Sep 2026 20:43:13 -0600")
Brigham Campbell <me@brighamcampbell.com> writes:
> Make git-contacts accept patch contents via stdin for better
> interoperability with other utilities. Read from stdin under the
> following circumstances:
>
> * stdin is not a terminal
> * argv is empty
>
> Cc: Junio C Hamano <gitster@pobox.com>
> Cc: Patrick Steinhardt <ps@pks.im>
It is unusual for these trailers to be here for this project.
> Signed-off-by: Brigham Campbell <me@brighamcampbell.com>
> ---
> diff --git a/contrib/contacts/git-contacts b/contrib/contacts/git-contacts
> index 85ad732fc0..52f6fbd044 100755
> --- a/contrib/contacts/git-contacts
> +++ b/contrib/contacts/git-contacts
> @@ -158,7 +158,7 @@ sub mailmap_contacts {
> return \%mapped;
> }
>
> -if (!@ARGV) {
> +if (!@ARGV && -t STDIN) {
> die "No input revisions or patch files\n";
> }
>
> @@ -178,6 +178,9 @@ for (@files) {
> if (@rev_args) {
> scan_rev_args(\%sources, \@rev_args)
> }
> +if (!@ARGV) {
> + scan_patches(\%sources, undef, \*STDIN);
> +}
Immediately before this hunk, there is
for (@files) {
scan_patch_file(\%sources, $_);
}
where both @rev_args and @files are derived from @ARGV. In fact,
once @ARGV is sifted into @rev_args and @files, nobody uses @ARGV
afterwards. @ARGV is used only to decide which things to work on
and how, and the decision is recorded in variables with more
meaningful names than @ARGV. After we are done with @ARGV, the
actions are carried out using variables with more meaningful names.
It would be nicer if you followed the pattern by doing something
like the attached patch instead.
By the way, there is a comment at the beginning of the file that
says:
# List people who might be interested in a patch. Useful as the argument to
# git-send-email --cc-cmd option, and in other situations.
#
# Usage: git contacts <file | rev-list option> ...
We'd probably need to update that part of the file as well.
contrib/contacts/git-contacts | 13 ++++++++++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git c/contrib/contacts/git-contacts w/contrib/contacts/git-contacts
index 85ad732fc0..f9e225b8b2 100755
--- c/contrib/contacts/git-contacts
+++ w/contrib/contacts/git-contacts
@@ -158,11 +158,15 @@ sub mailmap_contacts {
return \%mapped;
}
-if (!@ARGV) {
- die "No input revisions or patch files\n";
+my (@files, @rev_args, $read_from_stdin);
+
+if (!@ARGV)
+ if (-t STDIN) {
+ die "No input revisions or patch files\n";
+ }
+ $read_from_stdin = 1;
}
-my (@files, @rev_args);
for (@ARGV) {
if (-e) {
push @files, $_;
@@ -178,6 +182,9 @@ for (@files) {
if (@rev_args) {
scan_rev_args(\%sources, \@rev_args)
}
+if ($read_from_stdin) {
+ scan_patches(\%sources, undef, \*STDIN);
+}
my $toplevel = `git rev-parse --show-toplevel`;
chomp $toplevel;
next prev parent reply other threads:[~2026-09-15 4:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 2:43 [PATCH] git-contacts: allow inputting patch via stdin Brigham Campbell
2026-09-15 4:29 ` Junio C Hamano [this message]
2026-09-16 4:52 ` [PATCH v2] " Brigham Campbell
2026-09-16 14:25 ` Junio C Hamano
2026-09-17 6:56 ` Brigham Campbell
2026-09-24 1:25 ` [PATCH v3] " Brigham Campbell
2026-09-24 4:13 ` Junio C Hamano
2026-09-25 1:51 ` Brigham Campbell
2026-09-25 4:38 ` Junio C Hamano
2026-09-25 6:42 ` [PATCH v4] " Brigham Campbell
2026-09-25 16:09 ` Junio C Hamano
2026-09-29 5:47 ` [PATCH v5 0/2] " Brigham Campbell
2026-09-29 5:47 ` [PATCH v5 1/2] " Brigham Campbell
2026-09-29 19:29 ` Junio C Hamano
2026-10-02 4:44 ` Brigham Campbell
2026-09-29 5:47 ` [PATCH v5 2/2] git-contacts: add stdin functionality to docs Brigham Campbell
2026-09-29 16:30 ` [PATCH v5 0/2] git-contacts: allow inputting patch via stdin Junio C Hamano
2026-10-02 6:50 ` [PATCH v6] " Brigham Campbell
2026-10-02 14:50 ` 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=xmqqbj9z2l3y.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=me@brighamcampbell.com \
--cc=ps@pks.im \
/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.