Re: Git is not scalable with too many refs/*
- From
Johan Herland <johan@herland.net>
- Date
- Jun 14, 2011, 10:02 UTC
- Message-ID
- <201106141202.46720.johan@herland.net>
- In-Reply-To
- <BANLkTimNoh3-Jde_-arzwBa=aUR+KK3Xhw@mail.gmail.com>
On Tuesday 14 June 2011, Sverre Rabbelier wrote:
Show 9 quoted lines
> Heya, > > On Tue, Jun 14, 2011 at 06:41, Junio C Hamano <gitster@pobox.com> wrote: > > I would rather want to see if somebody can come up with a flexible > > reverse mapping feature around notes. It does not have to be > > completely generic, just being flexible enough is fine. > > Wouldn't it be enough to simply create a note on 'r651235' with as > contents the git ref?
Not quite sure what you mean by "create a note on 'r651235'". You could devise a scheme where you SHA1('r651235'), and then create a note on the resulting hash.
Notes are named by the SHA1 of the object they annotate, but there is no hard requirement (as long as you stay away from "git notes prune") that the SHA1 annotated actually exists as a valid Git object in your repo.
Hence, you can use notes to annotate _anything_ that can be uniquely reduced to a SHA1 hash.
...Johan
-- Johan Herland, <johan@herland.net> www.herland.net