On 2007-10-08 16:40:17 +0400, Dmitry Potapov wrote:
> On Mon, Oct 08, 2007 at 11:27:33AM +0200, Andreas Ericsson wrote:
>
> > A clone only fetches revs reachable from a ref, so pruning
> > immediately after a clone is completely pointless.
>
> Not true. git-clone copies the whole pack, so it can contain
> unreachable objects.
[...]
> git-clone -l test/.git test2
Try without the -l option and with a file:// URL:
git clone file:///path/to/test/.git test2
>From the git-clone man page:
--local::
-l::
When the repository to clone from is on a local machine, this
flag bypasses normal "git aware" transport mechanism and
clones the repository by making a copy of HEAD and everything
under objects and refs directories. The files under
`.git/objects/` directory are hardlinked to save space when
possible. This is now the default when the source repository
is specified with `/path/to/repo` syntax, so it essentially is
a no-op option. To force copying instead of hardlinking (which
may be desirable if you are trying to make a back-up of your
repository), but still avoid the usual "git aware" transport
mechanism, `--no-hardlinks` can be used.
--
Karl Hasselström, kha@xxxxxxxxxxx
www.treskal.com/kalle
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
