From: "Shawn O. Pearce" <spearce@spearce.org>
To: Marcus Griep <neoeinstein@gmail.com>
Cc: Derek Fawcus <dfawcus@cisco.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: [RFC] Plumbing-only support for storing object metadata
Date: Mon, 18 Aug 2008 16:28:00 -0700 [thread overview]
Message-ID: <20080818232800.GD9572@spearce.org> (raw)
In-Reply-To: <48AA0487.8050009@gmail.com>
Marcus Griep <neoeinstein@gmail.com> wrote:
> I was under the impression that tags were references to commit objects,
> and they to tree objects:
>
> tag -> commit -> tree
No. A tag can reference any object. See for example the
junio-gpg-pub tag in git.git, it references a blob, not a commit.
The linux-2.6.git tree has a tag which references a tree.
Tags may also reference other tags.
> Also, wouldn't this require large numbers tags, or the ability to multi-
> target tags?
Tag objects don't have to have names in the repository's ref space,
but it helps that they do when you are doing git-lost-found.
Having a tag in the database which shouldn't have a ref name in
refs/tags is more than a bit funny.
--
Shawn.
next prev parent reply other threads:[~2008-08-18 23:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-09 21:07 [RFC] Plumbing-only support for storing object metadata Jamey Sharp, Josh Triplett
2008-08-09 21:49 ` Scott Chacon
2008-08-10 3:51 ` Shawn O. Pearce
2008-08-10 11:20 ` Stephen R. van den Berg
2008-08-10 12:16 ` david
2008-08-10 14:50 ` Jan Hudec
2008-08-10 17:57 ` Stephen R. van den Berg
2008-08-10 18:11 ` Jan Hudec
2008-08-10 20:16 ` Stephen R. van den Berg
2008-08-10 22:34 ` Junio C Hamano
2008-08-10 23:10 ` david
2008-08-11 10:11 ` Stephen R. van den Berg
2008-08-16 6:21 ` Josh Triplett, Jamey Sharp
2008-08-16 7:56 ` david
2008-08-16 9:55 ` Junio C Hamano
2008-08-16 15:07 ` Jan Hudec
2008-08-18 6:12 ` Shawn O. Pearce
2008-08-18 23:06 ` Derek Fawcus
2008-08-18 23:18 ` Shawn O. Pearce
2008-08-18 23:23 ` Marcus Griep
2008-08-18 23:28 ` Shawn O. Pearce [this message]
2008-08-10 11:09 ` Jan Hudec
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=20080818232800.GD9572@spearce.org \
--to=spearce@spearce.org \
--cc=dfawcus@cisco.com \
--cc=git@vger.kernel.org \
--cc=neoeinstein@gmail.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).