public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Andrey Albershteyn <aalbersh@redhat.com>
Cc: linux-xfs@vger.kernel.org, Andrey Albershteyn <aalbersh@kernel.org>
Subject: Re: [PATCH v2 6/7] git-contributors: make revspec required and shebang fix
Date: Tue, 28 Jan 2025 09:44:47 -0800	[thread overview]
Message-ID: <20250128174447.GP1611770@frogsfrogsfrogs> (raw)
In-Reply-To: <20250122-update-release-v2-6-d01529db3aa5@kernel.org>

On Wed, Jan 22, 2025 at 04:01:32PM +0100, Andrey Albershteyn wrote:
> Without default value script will show help instead of just hanging
> waiting for input on stdin.

Is it useful to be able to do

	git-contributors < fubar.patch

?

For the single usecase of generating announcement emails it probably
doesn't matter though.

--D

> Shebang fix for system with different python location than the
> /usr/bin one.
> 
> Signed-off-by: Andrey Albershteyn <aalbersh@kernel.org>
> ---
>  tools/git-contributors.py | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/tools/git-contributors.py b/tools/git-contributors.py
> index 83bbe8ce0ee1dcbd591c6d3016d553fac2a7d286..628d6d0b4d8795e10b1317fa6fc91c6b98b21f3e 100755
> --- a/tools/git-contributors.py
> +++ b/tools/git-contributors.py
> @@ -1,4 +1,4 @@
> -#!/usr/bin/python3
> +#!/usr/bin/env python3
>  
>  # List all contributors to a series of git commits.
>  # Copyright(C) 2025 Oracle, All Rights Reserved.
> @@ -71,8 +71,7 @@ class find_developers(object):
>  
>  def main():
>      parser = argparse.ArgumentParser(description = "List email addresses of contributors to a series of git commits.")
> -    parser.add_argument("revspec", nargs = '?', default = None, \
> -            help = "git revisions to process.")
> +    parser.add_argument("revspec", help = "git revisions to process.")
>      parser.add_argument("--delimiter", type = str, default = '\n', \
>              help = "Separate each email address with this string.")
>      args = parser.parse_args()
> 
> -- 
> 2.47.0
> 
> 

  reply	other threads:[~2025-01-28 17:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-22 15:01 [PATCH v2 0/7] Update release.sh Andrey Albershteyn
2025-01-22 15:01 ` [PATCH v2 1/7] release.sh: add signing and fix outdated commands Andrey Albershteyn
2025-01-22 15:01 ` [PATCH v2 2/7] release.sh: add --kup to upload release tarball to kernel.org Andrey Albershteyn
2025-01-28 17:35   ` Darrick J. Wong
2025-01-22 15:01 ` [PATCH v2 3/7] release.sh: update version files make commit optional Andrey Albershteyn
2025-01-28 17:38   ` Darrick J. Wong
2025-01-22 15:01 ` [PATCH v2 4/7] release.sh: generate ANNOUNCE email Andrey Albershteyn
2025-01-28 17:38   ` Darrick J. Wong
2025-01-22 15:01 ` [PATCH v2 5/7] Add git-contributors script to notify about merges Andrey Albershteyn
2025-01-28 17:43   ` Darrick J. Wong
2025-01-22 15:01 ` [PATCH v2 6/7] git-contributors: make revspec required and shebang fix Andrey Albershteyn
2025-01-28 17:44   ` Darrick J. Wong [this message]
2025-01-22 15:01 ` [PATCH v2 7/7] release.sh: use git-contributors to --cc contributors Andrey Albershteyn
2025-01-28 18:01   ` Darrick J. Wong

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=20250128174447.GP1611770@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=aalbersh@kernel.org \
    --cc=aalbersh@redhat.com \
    --cc=linux-xfs@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