public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-6899] git-undescr.sh: Support full output of git-descr.sh. Date: Thu, 27 Jan 2022 18:35:24 +0000 (GMT) [thread overview] Message-ID: <20220127183524.0E27B3858039@sourceware.org> (raw) https://gcc.gnu.org/g:bb6a8d1d52dcaf5d25c4936623ed5cab8d6a24de commit r12-6899-gbb6a8d1d52dcaf5d25c4936623ed5cab8d6a24de Author: Martin Liska <mliska@suse.cz> Date: Thu Jan 27 19:27:51 2022 +0100 git-undescr.sh: Support full output of git-descr.sh. contrib/ChangeLog: * git-undescr.sh: Support full output of git-descr.sh. Diff: --- contrib/git-undescr.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/contrib/git-undescr.sh b/contrib/git-undescr.sh index 7d2efe1a8e7..9d882a6814e 100755 --- a/contrib/git-undescr.sh +++ b/contrib/git-undescr.sh @@ -3,8 +3,8 @@ # Script to undescribe a GCC revision o=$(git config --get gcc-config.upstream); -r=$(echo $1 | sed -n 's,^r\([0-9]\+\)-[0-9]\+$,\1,p'); -n=$(echo $1 | sed -n 's,^r[0-9]\+-\([0-9]\+\)$,\1,p'); +r=$(echo $1 | sed -n 's,^r\([0-9]\+\)-[0-9]\+\(-g[0-9a-f]\+\)\?$,\1,p'); +n=$(echo $1 | sed -n 's,^r[0-9]\+-\([0-9]\+\)\(-g[0-9a-f]\+\)\?$,\1,p'); test -z $r && echo Invalid id $1 && exit 1; h=$(git rev-parse --verify --quiet ${o:-origin}/releases/gcc-$r);
reply other threads:[~2022-01-27 18:35 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220127183524.0E27B3858039@sourceware.org \ --to=marxin@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).