From: Jakub Narebski <jnareb@gmail.com>
To: Chris Ridd <chris.ridd@isode.com>
Subject: Re: [PATCH] Improve sed portability
Date: Sun, 13 Jul 2008 13:00:34 -0700 (PDT) [thread overview]
Message-ID: <m34p80rm5w.fsf@localhost.localdomain> (raw)
In-Reply-To: <484FEF71.2030909@isode.com>
Chris Ridd <chris.ridd@isode.com> writes:
> Of course, using a plain old:
>
> echo "$1"
>
> should work well too. Why is printf being used here and not echo,
> anyway?
Uh, because 'echo -n' is not portable enough, and for some reason it
was though that there shouldn't be final newline?
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-07-13 20:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 13:09 [PATCH] Improve sed portability Chris Ridd
2008-06-11 14:04 ` Johannes Sixt
2008-06-11 15:29 ` Chris Ridd
2008-06-11 16:39 ` Jeff King
2008-06-12 7:46 ` Johannes Sixt
2008-06-12 8:29 ` Chris Ridd
2008-06-12 9:07 ` Jeff King
2008-07-13 20:00 ` Jakub Narebski [this message]
2008-06-12 8:33 ` Junio C Hamano
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=m34p80rm5w.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=chris.ridd@isode.com \
/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).