From: Richard Biener <richard.guenther@gmail.com>
To: Serge Belyshev <belyshev@depni.sinp.msu.ru>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] gcc_update: use gcc-descr git alias for revision string in gcc/REVISION
Date: Fri, 16 Jul 2021 09:06:01 +0200 [thread overview]
Message-ID: <CAFiYyc1=1tpvToKK_J0y-R5JzFfe85JvW14ChRaGOxte6-0TEA@mail.gmail.com> (raw)
In-Reply-To: <878s271je5.fsf@depni.sinp.msu.ru>
On Thu, Jul 15, 2021 at 9:12 PM Serge Belyshev
<belyshev@depni.sinp.msu.ru> wrote:
>
> This is to make development version string more readable, and
> to simplify navigation through gcc-testresults.
>
> Currently gcc_update uses git log --pretty=tformat:%p:%t:%H to
> generate version string, which is somewhat excessive since conversion
> to git because commit hashes are now stable.
>
> Even better, gcc-git-customization.sh script provides gcc-descr alias
> which makes prettier version string, and thus use it instead (or just
> abbreviated commit hash when the alias is not available).
>
> Before: [master revision b25edf6e6fe:e035f180ebf:7094a69bd62a14dfa311eaa2fea468f221c7c9f3]
> After: [master r12-2331]
>
> OK for mainline?
Can you instead open-code gcc-descr in this script?
> contrib/Changelog:
>
> * gcc_update: Use gcc-descr alias for revision string if it exists, or
> abbreviated commit hash instead. Drop "revision" from gcc/REVISION.
> ---
> contrib/gcc_update | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/contrib/gcc_update b/contrib/gcc_update
> index 80fac9fc995..8f712e37616 100755
> --- a/contrib/gcc_update
> +++ b/contrib/gcc_update
> @@ -332,7 +332,7 @@ case $vcs_type in
> exit 1
> fi
>
> - revision=`$GCC_GIT log -n1 --pretty=tformat:%p:%t:%H`
> + revision=`$GCC_GIT gcc-descr || $GCC_GIT log -n1 --pretty=tformat:%h`
> branch=`$GCC_GIT name-rev --name-only HEAD || :`
> ;;
>
> @@ -414,6 +414,6 @@ rm -f LAST_UPDATED gcc/REVISION
> date
> echo "`TZ=UTC date` (revision $revision)"
> } > LAST_UPDATED
> -echo "[$branch revision $revision]" > gcc/REVISION
> +echo "[$branch $revision]" > gcc/REVISION
>
> touch_files_reexec
next prev parent reply other threads:[~2021-07-16 7:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 19:12 Serge Belyshev
2021-07-16 7:06 ` Richard Biener [this message]
2021-07-16 7:29 ` Jakub Jelinek
2021-07-16 9:22 ` Richard Biener
2021-07-16 9:36 ` Jakub Jelinek
2021-07-16 9:39 ` Richard Biener
2021-07-16 10:37 ` [PATCH v2] gcc_update: use human readable name " Serge Belyshev
2021-07-19 10:39 ` Richard Biener
2021-07-19 10:47 ` Iain Sandoe
2021-07-19 11:09 ` Jakub Jelinek
2021-07-19 11:23 ` [PATCH v3] " Serge Belyshev
2021-09-06 9:49 ` Serge Belyshev
2021-09-06 9:54 ` Jakub Jelinek
2021-09-06 13:01 ` Serge Belyshev
2021-07-19 13:53 ` [PATCH] gcc_update: use gcc-descr git alias " Richard Earnshaw
2021-07-19 14:09 ` Jakub Jelinek
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='CAFiYyc1=1tpvToKK_J0y-R5JzFfe85JvW14ChRaGOxte6-0TEA@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=belyshev@depni.sinp.msu.ru \
--cc=gcc-patches@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).