From: Jakub Narebski <jnareb@gmail.com>
To: Vaclav Hanzl <hanzl@noel.feld.cvut.cz>
Cc: peff@peff.net, git@vger.kernel.org
Subject: Re: Document clone of clone ... bug??
Date: Sat, 14 Jun 2008 13:34:35 -0700 (PDT) [thread overview]
Message-ID: <m3skvfpxgp.fsf@localhost.localdomain> (raw)
In-Reply-To: <20080614.221511.74741328.hanzl@noel.feld.cvut.cz>
Vaclav Hanzl <hanzl@noel.feld.cvut.cz> writes:
> > The clone of clone does not have dangling objects; either it sees a ref
> > (because it is a branch in the clone) and it grabs the objects, or it
> > does not see it, in which case it does not download those objects.
>
> Yes, there should not be a dangling object, but I actually got one. I
> was surprised, but I thought it is just an undocumented benign behavior
> (optimization overkill - clone rather gets those objects instead of
> thinking what it needs).
[...]
> (cd B; git clone ../A/X)
_Local_ clone? This is result of optimization; in cloning over local
filesystem case git-clone simply hardlinks object database (if
possible) instead of transferring objects. This was only on request
in earlier versions of git.
You can use filr:// protocol to force generating of pack-file and
actual transfer of objects.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-06-14 20:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-14 13:05 Document clone of clone loosing branches? Vaclav Hanzl
2008-06-14 14:31 ` Jeff King
2008-06-14 20:15 ` Document clone of clone ... bug?? Vaclav Hanzl
2008-06-14 20:34 ` Jakub Narebski [this message]
2008-06-14 20:48 ` Vaclav Hanzl
2008-06-14 14:31 ` Document clone of clone loosing branches? Jakub Narebski
2008-06-14 14:44 ` Lea Wiemann
2008-06-14 21:36 ` Vaclav Hanzl
2008-06-14 22:18 ` Junio C Hamano
2008-06-15 7:18 ` Vaclav Hanzl
2008-06-14 23:03 ` Jakub Narebski
2008-06-15 8:40 ` Jakub Narebski
2008-06-15 13:05 ` [PATCH] Documentation: Note about the meaning of "clone" Robin Rosenberg
2008-06-15 13:39 ` Jakub Narebski
2008-06-15 13:52 ` Wincent Colaiuta
2008-06-15 16:31 ` Vaclav Hanzl
2008-06-15 17:03 ` Vaclav Hanzl
2008-06-15 19:12 ` Miklos Vajna
2008-06-15 20:14 ` Junio C Hamano
2008-06-15 13:05 ` PATCH] cvsimport: Clarification on the use of -r Robin Rosenberg
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=m3skvfpxgp.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=hanzl@noel.feld.cvut.cz \
--cc=peff@peff.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.