From: Kris Shannon <kris.shannon.kernel@gmail.com>
To: dwheeler@dwheeler.com
Cc: GIT Mailing List <git@vger.kernel.org>
Subject: Re: RT[3/3]: Reverse lookup of SHA1 references
Date: Fri, 29 Apr 2005 10:11:23 +1000 [thread overview]
Message-ID: <5d4799ae0504281711669ef900@mail.gmail.com> (raw)
In-Reply-To: <42717714.50601@dwheeler.com>
On 4/29/05, David A. Wheeler <dwheeler@dwheeler.com> wrote:
> Kris Shannon wrote:
> > There are a number of places where you want to find all the objects
> > which reference this particular object. AIUI this is not currently an easy
> > task. Some thought should be put into how to make these reverse
> > lookups fast.
> I have. Please look at my old postings. It turns out to be easy;
> just create a directory parallel to .git/objects, say:
> .git/reverse
> 00/
> 89123408312904819048390/
> 189412890892308290
> 238923849038329089
>
> Anyway you get the idea.
Seems reasonable.
> Linus does NOT want renames noted; see the old emails on that.
> It's not clear this is such a good idea, but he's adamant.
> He thinks this can be handled by merge.
> If not, it can be added later.
I realize that this is not a priority for linus, I was suggesting that
it be added as a separate object type. I think that many of the
extra metadata could be usefully added as other object types.
These can be optional and/or added after the fact.
> --- David A. Wheeler
>
--
Kris Shannon <kris.shannon.kernel@gmail.com>
prev parent reply other threads:[~2005-04-29 0:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 12:59 RT[0/3]: Some related random thoughts Kris Shannon
2005-04-28 13:34 ` RT[2/3]: Rename/Code-movement Tracking Kris Shannon
2005-04-28 13:47 ` RT[1/3]: Alternate Encodings (esp. Delta Compression) Kris Shannon
2005-04-28 13:54 ` RT[3/3]: Reverse lookup of SHA1 references Kris Shannon
[not found] ` <42717714.50601@dwheeler.com>
2005-04-29 0:11 ` Kris Shannon [this message]
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=5d4799ae0504281711669ef900@mail.gmail.com \
--to=kris.shannon.kernel@gmail.com \
--cc=dwheeler@dwheeler.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).