public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "egallager 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: Tue, 08 Mar 2022 17:07:42 +0000 [thread overview] Message-ID: <bug-102664-4-JEdUbPfCWW@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 #19 from Eric Gallager <egallager at gcc dot gnu.org> --- (In reply to Martin Liška from comment #10) > > I still get "expr: syntax error" when trying to do `git gcc-descr 716bb02b` > > after re-running `sh ./contrib/gcc-git-customization.sh` > > Ok, so can you please run: > > $ bash -x ./contrib/git-descr.sh 716bb02b > Ok, I've updated; output of that is now: $ bash -x ./contrib/git-descr.sh 716bb02b + short=no + long=no + c=master + for arg in '"$@"' + case "$arg" in + c=716bb02b + test xno = xyes + test xno = xyes ++ git describe --all --abbrev=14 --match 'basepoints/gcc-[0-9]*' 716bb02b ++ sed -n 's,^\(tags/\)\?basepoints/gcc-,r,p' + r= + expr no : 'r[0-9]\+$' + test -n ++ git config --get gcc-config.upstream + o=origin ++ echo ++ sed -n 's,^r\([0-9]\+\)-[0-9]\+\(-g[0-9a-f]\+\)\?$,\1,p' + rr= + git rev-parse --verify --quiet origin/releases/gcc- + m=master + git merge-base --is-ancestor 716bb02b origin/master + echo $ > What OS do you use? macOS 11.6.4 (Big Sur)
next prev parent reply other threads:[~2022-03-08 17:07 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 [this message] 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 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-JEdUbPfCWW@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: 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).