From: Johannes Sixt <j.sixt@viscovery.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Reece Dunn <msclrhd@googlemail.com>, Git <git@vger.kernel.org>
Subject: Re: git clone questions relating to cpio
Date: Tue, 02 Oct 2007 08:11:24 +0200 [thread overview]
Message-ID: <4701E10C.7050405@viscovery.net> (raw)
In-Reply-To: <7vwsu6pg0v.fsf@gitster.siamese.dyndns.org>
Junio C Hamano schrieb:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
>> On Mon, 1 Oct 2007, Reece Dunn wrote:
>>
>>> I am running a Linux From Scratch 6.2 system that does not have cpio
>>> installed on it. This means that I can't clone a local repository
>>> unless I install cpio.
>> You might be interested in the workaround Hannes did in mingw.git; he made
>> a wrapper script called 'cpio' using 'tar'.
>
> I think that may be good enough as workaround, but I do not
> think you would get the space saving from hardlinks that way.
FWIW, I'm thinking about changing the cpio -p (passthrough) part to use
'cp -l --parents --target-directory=...' instead of tar; this gives us hard
links, even on NTFS. But it needs GNU's cp, of course.
-- Hannes
next prev parent reply other threads:[~2007-10-02 6:11 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
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 [this message]
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=4701E10C.7050405@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).