From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: Martin Jambor <mjambor@suse.cz>, Jakub Jelinek <jakub@redhat.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] contrib: Put gcc-descr and gcc-undescr to file.
Date: Thu, 27 Jan 2022 15:51:02 +0000 [thread overview]
Message-ID: <CAH6eHdSnAjSno-YE7PC5VHd2Gfhv5EgT6_quPan2-dZinzDk5Q@mail.gmail.com> (raw)
In-Reply-To: <28f9be5c-c9a7-9e33-1ba0-49579695c912@suse.cz>
On Thu, 27 Jan 2022, 15:06 Martin Liška, <mliska@suse.cz> wrote:
> Hello.
>
> I've finished Martin's work and put the 2 aliases into files. The
> git-undescr.sh is basically
> unchanged, while I added better option parsing for git-descr.sh script so
> that it supports:
>
> $ git gcc-descr
> r12-6895-g14f339894db6ca
>
> $ git gcc-descr HEAD~10
> r12-6886-geaa59070343326
>
> $ git gcc-descr HEAD~10 --long
> r12-6886-geaa5907034332649c918f0579da805b6e786aa47
>
> $ git gcc-descr --short HEAD~10 --long
> r12-6886
>
> $ git gcc-descr --short --short --long HEAD~10
> r12-6886
>
> Ready to be installed?
>
> + expr match ${r:-no} '^r[0-9]\+$' >/dev/null && r=${r}-0-g$(git
rev-parse $c);
Please remove the ^ from the 'expr' regex. The regex for an expr match can
only match at the beginning, so the ^ is implicit, but some implementations
ignore it (e.g. on Linux) and others march it as a normal character (e.g.
macOS).
prev parent reply other threads:[~2022-01-27 15:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 11:01 [PATCH] contrib: git gcc-descr defaulting to print hash Martin Liška
2021-10-08 11:12 ` Jakub Jelinek
2021-10-11 12:32 ` [RFC] Port git gcc-descr to Python Martin Liška
2021-10-12 8:59 ` Martin Liška
2021-10-14 9:06 ` Tobias Burnus
2021-10-14 9:19 ` Jakub Jelinek
2021-10-18 9:01 ` Martin Liška
2022-01-19 11:01 ` Martin Liška
2022-01-19 12:49 ` Martin Jambor
2022-01-19 13:17 ` Martin Liška
2022-01-19 16:54 ` Eric Gallager
2022-01-27 15:06 ` [PATCH] contrib: Put gcc-descr and gcc-undescr to file Martin Liška
2022-01-27 15:35 ` Jakub Jelinek
2022-01-27 17:44 ` Martin Liška
2022-01-27 15:51 ` Jonathan Wakely [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=CAH6eHdSnAjSno-YE7PC5VHd2Gfhv5EgT6_quPan2-dZinzDk5Q@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=mjambor@suse.cz \
--cc=mliska@suse.cz \
/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).