From: Avery Pennarun <apenwarr@gmail.com>
To: martin f krafft <madduck@madduck.net>
Cc: Johan Herland <johan@herland.net>, git@vger.kernel.org
Subject: Re: Using trees for metatagging
Date: Thu, 18 Feb 2010 18:06:42 -0500 [thread overview]
Message-ID: <32541b131002181506v1d28526cpf8491994868272af@mail.gmail.com> (raw)
In-Reply-To: <20100218225758.GL9756@lapse.rw.madduck.net>
On Thu, Feb 18, 2010 at 5:57 PM, martin f krafft <madduck@madduck.net> wrote:
> I am aware of notes, but so far I stayed away from them, simply
> because it seems hackish to represent tag trees as text when dealing
> with a tool that is essentially all about trees and refs.
I think you're using the wrong definition of hacky vs. elegant. A
"tree" is really just a file containing a list of objects. A "ref" is
just a file that contains an object id.
So checking in a file that contains a list of object ids (or
filenames) is perfectly appropriate.
Have fun,
Avery
next prev parent reply other threads:[~2010-02-18 23:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 4:12 Using trees for metatagging martin f krafft
2010-02-18 18:57 ` Avery Pennarun
2010-02-18 22:53 ` martin f krafft
2010-02-18 21:00 ` Johan Herland
2010-02-18 22:57 ` martin f krafft
2010-02-18 23:06 ` Avery Pennarun [this message]
2010-02-18 23:25 ` martin f krafft
2010-02-18 23:32 ` Avery Pennarun
2010-02-19 0:43 ` Johan Herland
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=32541b131002181506v1d28526cpf8491994868272af@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=johan@herland.net \
--cc=madduck@madduck.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).