git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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:32:31 -0500	[thread overview]
Message-ID: <32541b131002181532h79d3250fid5984f46f82b71f9@mail.gmail.com> (raw)
In-Reply-To: <20100218232523.GD22371@lapse.rw.madduck.net>

On Thu, Feb 18, 2010 at 6:25 PM, martin f krafft <madduck@madduck.net> wrote:
> also sprach Avery Pennarun <apenwarr@gmail.com> [2010.02.19.1206 +1300]:
>> So checking in a file that contains a list of object ids (or
>> filenames) is perfectly appropriate.
>
> Indeed. But Git provides a lot of tools to manipulate all those,
> which I would not be able to reuse in the text-file approach.

But you're talking about using a nonstandard approach anyway (unless
you use git-notes).  So you'd end up rolling your own code with git's
plumbing anyway, which you can do just as easily with a text file full
of object ids.

Once you have an object id, there are plenty of existing git commands
to do whatever you want.

Have fun,

Avery

  reply	other threads:[~2010-02-18 23:32 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
2010-02-18 23:25       ` martin f krafft
2010-02-18 23:32         ` Avery Pennarun [this message]
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=32541b131002181532h79d3250fid5984f46f82b71f9@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).