Re: [PATCH] git-clone: use cpio's --quiet flag

Jeff King [off-list ref] writes:

On Sat, Aug 04, 2007 at 11:27:04AM -0700, Junio C Hamano wrote:

quoted

Try cloning across filesystem boundaries so that you do not get
a hardlink -- you will get block count of the copy ;-)

I see, though the hardlink warning is a bit much.

$ git-clone /path/on/fs/one /path/on/fs/two
Initialized empty Git repository in /path/on/fs/two/.git/
Warning: -l asked but cannot hardlink to /path/on/fs/one/.git
36634 blocks

True; -l is not given explicitly in your example.  Should be
trivial to fix.

On Sun, Aug 05, 2007 at 01:36:29AM -0700, Junio C Hamano wrote:

quoted

I see, though the hardlink warning is a bit much.

$ git-clone /path/on/fs/one /path/on/fs/two
Initialized empty Git repository in /path/on/fs/two/.git/
Warning: -l asked but cannot hardlink to /path/on/fs/one/.git
36634 blocks

True; -l is not given explicitly in your example.  Should be
trivial to fix.

Ah, indeed, I had assumed that it came from cpio (which also uses the -l
flag!), but reading the code, it's us. Given that "-l" is now the
default, and we silently downgrade to copying anyway, I don't see the
point of having any warning at all. Unless, I guess, for those people
who are still using "-l" even though it's a noop.

-Peff