From: Junio C Hamano <gitster@pobox.com>
To: Johan Herland <johan@herland.net>
Cc: git@vger.kernel.org, Reece Dunn <msclrhd@googlemail.com>
Subject: Re: [PATCH] Mention 'cpio' dependency in INSTALL
Date: Tue, 02 Oct 2007 17:14:25 -0700 [thread overview]
Message-ID: <7v1wcdjbq6.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <200710030142.30062.johan@herland.net> (Johan Herland's message of "Wed, 03 Oct 2007 01:42:29 +0200")
Johan Herland <johan@herland.net> writes:
> reveals that cpio is not mentioned anywhere in the documentation,
> nor in the requirements section of the INSTALL file.
Thanks.
We use many other tools that are typically found in bog-standard
UNIX environments, like sed, echo, cat, sort, etc. and we do not
list them in the INSTALL file (nor we would want to). cpio used
to be in the "bog standard" category but perhaps Linux distros
do not install it by default, so it is worth listing it there.
Are there other commands we rely on that may not be universally
installed? I myself consider "cut" to be in the category, but
other than that I do not think of anything offhand.
next prev parent reply other threads:[~2007-10-03 0:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 19:28 git clone questions relating to cpio Reece Dunn
2007-10-01 21:42 ` Johan Herland
2007-10-02 21:09 ` Reece Dunn
2007-10-02 23:42 ` [PATCH] Mention 'cpio' dependency in INSTALL Johan Herland
2007-10-03 0:14 ` Junio C Hamano [this message]
2007-10-03 6:09 ` Chris Larson
2007-10-03 7:40 ` Miklos Vajna
2007-10-03 8:27 ` [PATCH v2] INSTALL: Update section on external dependencies Johan Herland
2007-10-03 15:56 ` Johannes Schindelin
2007-10-03 16:05 ` Shawn O. Pearce
2007-10-01 23:23 ` git clone questions relating to cpio Johannes Schindelin
2007-10-01 23:32 ` Junio C Hamano
2007-10-02 6:11 ` Johannes Sixt
2007-10-02 6:23 ` 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=7v1wcdjbq6.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=johan@herland.net \
--cc=msclrhd@googlemail.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).