public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi 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: Wed, 09 Mar 2022 14:13:27 +0000	[thread overview]
Message-ID: <bug-102664-4-7evPHptfZq@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 #32 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #30)
> I'd have done printf "%s [%s]?" "$question" "$default" instead, but they're
> equivalent.

Oops, equivalent except for the missing space after the question mark in my
version.

There are still other issues on Solaris though:


$ PATH=/usr/xpg4/bin:$PATH ./contrib/gcc-git-customization.sh 
Your name [Jonathan Wakely]? 
Your email address (for git commits) [jwakely@redhat.com]? 
Local name for upstream repository [origin]? 
sed: illegal option -- r
Usage:  sed [-n] script [file...]
        sed [-n] [-e script]...[-f script_file]...[file...]
Account name on gcc.gnu.org (for your personal branches area) [remote_id]? redi
./contrib/gcc-git-customization.sh[16]: eval[1]: =redi: not found [No such file
or directory]

Local branch prefix for personal branches you want to share
(local branches starting <prefix>/ can be pushed directly to your
personal area on the gcc server) [me]? 

Install prepare-commit-msg git hook for 'git commit-mklog' alias [yes]? 
fatal: ambiguous argument 'hooks': unknown revision or path not in the working
tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
cp: illegal option -- git-path
cp: Insufficient arguments (1)
Usage: cp [-f] [-i] [-p] [-@] [-/] f1 f2
       cp [-f] [-i] [-p] [-@] [-/] f1 ... fn d1
       cp -r|-R [-H|-L|-P] [-f] [-i] [-p] [-@] [-/] d1 ... dn-1 dn
install: cp --git-path
/export/home/jwakely/src/gcc/contrib/prepare-commit-msg/--git-path failed 
sed: illegal option -- r
Usage:  sed [-n] script [file...]
        sed [-n] [-e script]...[-f script_file]...[file...]
Setting up tracking for personal namespace  in remotes/users/me
fatal: Invalid refspec '+refs/users//heads/*:refs/remotes/users/me/*'


I'll look into those ...

  parent reply	other threads:[~2022-03-09 14:13 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 [this message]
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-7evPHptfZq@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).