From: Marcus Griep <neoeinstein@gmail.com>
To: Derek Fawcus <dfawcus@cisco.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [RFC] Plumbing-only support for storing object metadata
Date: Mon, 18 Aug 2008 19:23:51 -0400 [thread overview]
Message-ID: <48AA0487.8050009@gmail.com> (raw)
In-Reply-To: <20080818230646.GA11044@cisco.com>
Derek Fawcus wrote:
> My other hacky thought was that tag object could be overloaded for
> this purpose. It is already sort of an indirect object, but seems
> to be limited to appearing at the edge of the graph.
>
> If we could say have:
>
> commit -> tag -> tree
>
> then arbitrary data could be stored in the tag, similarly this
> could be extended for when a tree or blob object is expected
> (I'm not sure about the blob case).
I was under the impression that tags were references to commit objects,
and they to tree objects:
tag -> commit -> tree
Also, wouldn't this require large numbers tags, or the ability to multi-
target tags?
--
Marcus Griep
GPG Key ID: 0x5E968152
——
http://www.boohaunt.net
את.ψο´
next prev parent reply other threads:[~2008-08-18 23:25 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 [this message]
2008-08-18 23:28 ` Shawn O. Pearce
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=48AA0487.8050009@gmail.com \
--to=neoeinstein@gmail.com \
--cc=dfawcus@cisco.com \
--cc=git@vger.kernel.org \
/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).