From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: git@vger.kernel.org
Subject: Re: [PATCH] git-rebase.sh: Use POSIX/Susv command substitution instead of backticks
Date: Wed, 6 Feb 2008 09:23:06 +0000 (UTC) [thread overview]
Message-ID: <loom.20080206T092136-104@post.gmane.org> (raw)
In-Reply-To: alpine.LSU.1.00.0802052305080.8543@racer.site
Johannes Schindelin <Johannes.Schindelin <at> gmx.de> writes:
> > > On Wed, 6 Feb 2008, Jari Aalto wrote:
> > >
> > >> Use redable $(<command>) syntax instead of backtics in code. See The
> > >> Open Group Base Specifications Issue 6, IEEE Std 1003.1, 2004 Edition
> And then you have to do it for all scripts in one go. Mind you, it is not
> really complicated: just one call to perl.
You still have to check all backslashes within the changed command; some you
may now have to remove.
Cheers,
Ralf
prev parent reply other threads:[~2008-02-06 9:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 22:08 [PATCH] git-rebase.sh: Use POSIX/Susv command substitution instead of backticks Jari Aalto
2008-02-05 22:27 ` Johannes Schindelin
2008-02-05 22:53 ` Jari Aalto
2008-02-05 23:06 ` Johannes Schindelin
2008-02-06 0:59 ` Junio C Hamano
2008-02-06 2:03 ` Junio C Hamano
2008-02-06 9:23 ` Ralf Wildenhues [this message]
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=loom.20080206T092136-104@post.gmane.org \
--to=ralf.wildenhues@gmx.de \
--cc=git@vger.kernel.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