public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/102664] contrib/gcc-git-customization.sh uses echo -n, which isn't portable
Date: Thu, 10 Mar 2022 08:43:29 +0000 [thread overview]
Message-ID: <bug-102664-4-zKxS8M3RwZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102664-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102664
--- Comment #34 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:ff060ef08cfc3e48e70071cb63449b62a86f9d6f
commit r12-7575-gff060ef08cfc3e48e70071cb63449b62a86f9d6f
Author: Jakub Jelinek <jakub@redhat.com>
Date: Thu Mar 10 09:42:03 2022 +0100
contrib: Fix up git-descr.sh regression [PR102664]
On Wed, Mar 09, 2022 at 12:40:24PM -0500, Patrick Palka via Gcc-patches
wrote:
> On Wed, Mar 9, 2022 at 8:54 AM Mikael Morin <morin-mikael@orange.fr>
wrote:
> > Le 08/03/2022 à 18:58, Jonathan Wakely via Gcc-patches a écrit :
> > > Replace \([0-9]\+\) with \([0-9][0-9]*\) or with \([1-9][0-9]*\) in
release branch numbers, where
> > > a leading zero does not occur.
> > >
> > Note that you also changed some gcc-[0-9]* to gcc-[1-9]*, which is a
> > typo/thinko I guess? It looks like it wouldnât match gcc-10 any more
> > for exampleâ¦
>
> Perhaps related to this, I noticed the following
> git gcc-descr ea1ce0d163ea1d63b6837144ae4be51d92630007
> now fails with
> fatal: No tags can describe 'ea1ce0d163ea1d63b6837144ae4be51d92630007'.
> instead of outputting
> r0-52309-gea1ce0d163ea1d
That is because of those [0-9] to [1-9] changes which prevent
basepoints/gcc-0 from working. While basepoints/gcc-005 etc. are certainly
unexpected, basepoints/gcc-0 needs to work.
2022-03-10 Jakub Jelinek <jakub@redhat.com>
PR other/102664
* git-descr.sh: Replace all [1-9] occurrences with [0-9].
* git-undescr.sh: Likewise.
next prev parent reply other threads:[~2022-03-10 8:43 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 16:03 [Bug other/102664] New: " egallager at gcc dot gnu.org
2021-10-09 18:26 ` [Bug other/102664] " pinskia at gcc dot gnu.org
2021-11-02 5:41 ` egallager at gcc dot gnu.org
2021-11-17 23:45 ` egallager at gcc dot gnu.org
2022-01-19 16:52 ` egallager at gcc dot gnu.org
2022-01-20 8:07 ` marxin at gcc dot gnu.org
2022-01-20 12:05 ` egallager at gcc dot gnu.org
2022-01-20 12:47 ` redi at gcc dot gnu.org
2022-01-27 21:05 ` redi at gcc dot gnu.org
2022-03-08 16:21 ` egallager at gcc dot gnu.org
2022-03-08 16:25 ` marxin at gcc dot gnu.org
2022-03-08 16:37 ` redi at gcc dot gnu.org
2022-03-08 16:40 ` redi at gcc dot gnu.org
2022-03-08 16:41 ` redi at gcc dot gnu.org
2022-03-08 16:42 ` marxin at gcc dot gnu.org
2022-03-08 16:45 ` redi at gcc dot gnu.org
2022-03-08 16:47 ` redi at gcc dot gnu.org
2022-03-08 16:48 ` cvs-commit at gcc dot gnu.org
2022-03-08 16:48 ` redi at gcc dot gnu.org
2022-03-08 17:07 ` egallager at gcc dot gnu.org
2022-03-08 17:16 ` redi at gcc dot gnu.org
2022-03-08 17:22 ` redi at gcc dot gnu.org
2022-03-08 17:35 ` redi at gcc dot gnu.org
2022-03-08 17:46 ` redi at gcc dot gnu.org
2022-03-08 17:58 ` redi at gcc dot gnu.org
2022-03-09 0:20 ` cvs-commit at gcc dot gnu.org
2022-03-09 0:21 ` redi at gcc dot gnu.org
2022-03-09 0:25 ` egallager at gcc dot gnu.org
2022-03-09 11:48 ` rearnsha at gcc dot gnu.org
2022-03-09 12:17 ` rearnsha at gcc dot gnu.org
2022-03-09 14:09 ` redi at gcc dot gnu.org
2022-03-09 14:10 ` redi at gcc dot gnu.org
2022-03-09 14:13 ` redi at gcc dot gnu.org
2022-03-09 17:14 ` redi at gcc dot gnu.org
2022-03-10 8:43 ` cvs-commit at gcc dot gnu.org [this message]
2022-03-10 11:49 ` cvs-commit at gcc dot gnu.org
2022-03-11 11:37 ` rearnsha at gcc dot gnu.org
2022-03-11 12:25 ` marxin at gcc dot gnu.org
2022-03-11 14:32 ` egallager at gcc dot gnu.org
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=bug-102664-4-zKxS8M3RwZ@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).