public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ken Matsui <kmatsui@cs.washington.edu>
To: gcc-patches@gcc.gnu.org
Cc: Ken Matsui <kmatsui@gcc.gnu.org>,
	Jason Merrill <jason@redhat.com>,
	 Jonathan Wakely <jwakely@redhat.com>
Subject: Re: [PATCH] contrib/gcc-changelog/git_check_commit.py: Implement --num-commits
Date: Thu, 14 Mar 2024 00:57:23 -0700	[thread overview]
Message-ID: <CAML+3pVz8pMfasGmcVuvR4bZ811S2kdonUevUPS1tXifHqdV8A@mail.gmail.com> (raw)
In-Reply-To: <8d06dede-7a9b-afd0-8bcd-6e0bdc497463@idea>

On Fri, Mar 8, 2024 at 8:42 AM Patrick Palka <ppalka@redhat.com> wrote:
>
> On Wed, 28 Feb 2024, Ken Matsui wrote:
>
> > This patch implements a --num-commits (-n) flag for shorthand for
> > the range of hash~N..hash commits.

Ping.

> >
> > contrib/ChangeLog:
> >
> >       * gcc-changelog/git_check_commit.py: Implement --num-commits.
>
> LGTM
>
> >
> > Signed-off-by: Ken Matsui <kmatsui@gcc.gnu.org>
> > ---
> >  contrib/gcc-changelog/git_check_commit.py | 15 +++++++++++++++
> >  1 file changed, 15 insertions(+)
> >
> > diff --git a/contrib/gcc-changelog/git_check_commit.py b/contrib/gcc-changelog/git_check_commit.py
> > index 8cca9f439a5..22e032e8b38 100755
> > --- a/contrib/gcc-changelog/git_check_commit.py
> > +++ b/contrib/gcc-changelog/git_check_commit.py
> > @@ -22,6 +22,12 @@ import argparse
> >
> >  from git_repository import parse_git_revisions
> >
> > +def nonzero_uint(value):
> > +    ivalue = int(value)
> > +    if ivalue <= 0:
> > +        raise argparse.ArgumentTypeError('%s is not a non-zero positive integer' % value)
> > +    return ivalue
> > +
> >  parser = argparse.ArgumentParser(description='Check git ChangeLog format '
> >                                   'of a commit')
> >  parser.add_argument('revisions', default='HEAD', nargs='?',
> > @@ -33,8 +39,17 @@ parser.add_argument('-p', '--print-changelog', action='store_true',
> >                      help='Print final changelog entires')
> >  parser.add_argument('-v', '--verbose', action='store_true',
> >                      help='Print verbose information')
> > +parser.add_argument('-n', '--num-commits', type=nonzero_uint, default=1,
> > +                    help='Number of commits to check (i.e. shorthand for '
> > +                    'hash~N..hash)')
> >  args = parser.parse_args()
> >
> > +if args.num_commits > 1:
> > +    if '..' in args.revisions:
> > +        print('ERR: --num-commits and range of revisions are mutually exclusive')
> > +        exit(1)
> > +    args.revisions = '{0}~{1}..{0}'.format(args.revisions, args.num_commits)
> > +
> >  retval = 0
> >  for git_commit in parse_git_revisions(args.git_path, args.revisions):
> >      res = 'OK' if git_commit.success else 'FAILED'
> > --
> > 2.44.0
> >
> >
>

  reply	other threads:[~2024-03-14  7:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-28 21:09 Ken Matsui
2024-03-08 16:42 ` Patrick Palka
2024-03-14  7:57   ` Ken Matsui [this message]
2024-05-06 13:25     ` Ken Matsui
2024-05-06 16:20       ` Jason Merrill
2024-05-06 16:26         ` Ken Matsui

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=CAML+3pVz8pMfasGmcVuvR4bZ811S2kdonUevUPS1tXifHqdV8A@mail.gmail.com \
    --to=kmatsui@cs.washington.edu \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.com \
    --cc=jwakely@redhat.com \
    --cc=kmatsui@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).