git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon 'corecode' Schubert <corecode@fs.ei.tum.de>
To: Junio C Hamano <junkio@cox.net>
Cc: "Horst H. von Brand" <vonbrand@inf.utfsm.cl>, git@vger.kernel.org
Subject: Re: [PATCH] Replace "echo -n" with printf in shell scripts.
Date: Thu, 18 Jan 2007 01:02:58 +0100	[thread overview]
Message-ID: <45AEB932.3060509@fs.ei.tum.de> (raw)
In-Reply-To: <7vk5zlsglk.fsf@assigned-by-dhcp.cox.net>

[-- Attachment #1: Type: text/plain, Size: 717 bytes --]

Junio C Hamano wrote:
>>> We have done this already so it might be too late to raise this
>>> question, but does everybody have printf?
> The problematic are less common ones, ranging from (not so less
> common) OSX, Solaris to (much less common) AIX that some people
> seem to run git on (or at least compile git for).

printf(1) is part of POSIX/SUSv3, so systems *should* have it.

cheers
  simon

-- 
Serve - BSD     +++  RENT this banner advert  +++    ASCII Ribbon   /"\
Work - Mac      +++  space for low €€€ NOW!1  +++      Campaign     \ /
Party Enjoy Relax   |   http://dragonflybsd.org      Against  HTML   \
Dude 2c 2 the max   !   http://golden-apple.biz       Mail + News   / \


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  parent reply	other threads:[~2007-01-18  0:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-16  1:31 [PATCH] Replace "echo -n" with printf in shell scripts Jason Riedy
2007-01-16  2:46 ` Junio C Hamano
2007-01-16  3:03   ` Jason Riedy
2007-01-16  3:09   ` Eric Blake
2007-01-17 16:29   ` Horst H. von Brand
2007-01-17 17:33     ` Junio C Hamano
2007-01-17 18:00       ` Brian Gernhardt
2007-01-17 18:07       ` Julian Phillips
2007-01-17 20:17         ` Horst H. von Brand
2007-01-18  0:02       ` Simon 'corecode' Schubert [this message]
2007-01-18  0:13         ` 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=45AEB932.3060509@fs.ei.tum.de \
    --to=corecode@fs.ei.tum.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=vonbrand@inf.utfsm.cl \
    /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).