From: Jon Seymour <jon.seymour@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Johan Herland <johan@herland.net>, git@vger.kernel.org
Subject: A question about the tree associated with a git notes commit
Date: Wed, 10 Feb 2010 17:16:55 +1100 [thread overview]
Message-ID: <2cfc40321002092216p5cbf432bs3766d40858f9bf3a@mail.gmail.com> (raw)
Is the tree associated with a notes commit limited to a single level,
or is there some attempt to balance the tree as the number of
annotated objects increases?
If the tree is currently restricted to a single level, is this
eventually going to be a problem as the number of annotated objects
continues to grow?
Apologies if this question is answered with trivial analysis of the
code, I admittedly haven't done that.
jon.
next reply other threads:[~2010-02-10 6:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 6:16 Jon Seymour [this message]
2010-02-10 7:01 ` A question about the tree associated with a git notes commit Junio C Hamano
2010-02-10 8:21 ` Jon Seymour
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=2cfc40321002092216p5cbf432bs3766d40858f9bf3a@mail.gmail.com \
--to=jon.seymour@gmail.com \
--cc=git@vger.kernel.org \
--cc=johan@herland.net \
--cc=peff@peff.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).