From: Josh Triplett <josh@joshtriplett.org>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: Properties of trees referencing commit objects (mode 160000)?
Date: Sun, 20 Mar 2016 11:45:24 -0700 [thread overview]
Message-ID: <20160320184524.GA16064@x> (raw)
In-Reply-To: <20160320041803.GC18312@sigill.intra.peff.net>
On Sun, Mar 20, 2016 at 12:18:04AM -0400, Jeff King wrote:
> On Sat, Mar 19, 2016 at 03:13:48PM -0700, Josh Triplett wrote:
>
> > I'm building some tools to track commit objects, and I'm thinking of
> > using submodule-style references to commit objects in tree objects (mode
> > 160000) to do so. I'm trying to figure out some of the properties of
> > that.
> >
> > Can a commit object referenced that way live in the same repository,
> > rather than some external repository?
>
> Yes, it can be in the same repository, but...
Will git clone/checkout/etc handle it properly in that case, in the
absence of a .gitmodules file? Or would it only work with custom tools?
> > Will git treat such a reference as keeping the commit object (and
> > everything recursively referenced by it) live and reachable? If that
> > commit object is only reachable by the tree, and not by following the
> > parents of any commit directly referenced from refs/*, will git discard
> > it as unreachable?
>
> No, we do not follow "gitlinks" like this for reachability. Neither for
> pruning, nor for object transfer via push/fetch. So you'd need to have a
> separate reference to it (or history containing it).
Argh. If I have a pile of disconnected commits, is there anything git
*would* follow to see them, other than a pile of refs?
I suppose I could artificially generate a stack of merge commits with
those otherwise disconnect commits as parents, which would let me
reference them all from a single ref. Still unsatisfying, though.
Also, thanks, "gitlink" was the term I was trying to think of.
(I'd also be tempted to ask whether a patch to teach git to follow
gitlinks for reachability and/or object transfer would be acceptable.)
next prev parent reply other threads:[~2016-03-20 18:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-19 22:13 Properties of trees referencing commit objects (mode 160000)? Josh Triplett
2016-03-20 4:18 ` Jeff King
2016-03-20 18:45 ` Josh Triplett [this message]
2016-03-20 20:07 ` Jeff King
2016-03-20 23:22 ` Josh Triplett
2016-03-21 5:57 ` Jeff King
2016-03-21 15:36 ` Josh Triplett
2016-03-20 22:30 ` Junio C Hamano
2016-03-20 22:43 ` Josh Triplett
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=20160320184524.GA16064@x \
--to=josh@joshtriplett.org \
--cc=git@vger.kernel.org \
--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 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).