From: Jason Riedy <ejr@EECS.Berkeley.EDU>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Use printf rather than echo -n.
Date: Tue, 06 Dec 2005 19:31:43 -0800 [thread overview]
Message-ID: <21616.1133926303@lotus.CS.Berkeley.EDU> (raw)
In-Reply-To: <7vfyp5zmqe.fsf@assigned-by-dhcp.cox.net>
And Junio C Hamano writes:
- Perhaps printf '%s' "$blah" to futureproof, instead of just
- saying printf "$blah"?
Definitely more likely to stay correct. I'm just lazy.
- <rant mode on>
- While I do not have anything aginst system without "sane" echo,
- I really do not like it. Not your solution, but *having to do*
- something like that.
Um, you think the wrong one is sane. ;) Why should echo
in Bourne shell take C-shell arguments? (I blame AT&T for
their crappy licensing.)
Jason
next prev parent reply other threads:[~2005-12-07 3:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 22:21 [PATCH] Use printf rather than echo -n Jason Riedy
2005-12-07 2:04 ` Junio C Hamano
2005-12-07 3:31 ` Jason Riedy [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-08 8:02 linux
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=21616.1133926303@lotus.CS.Berkeley.EDU \
--to=ejr@eecs.berkeley.edu \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 NNTP newsgroup(s).