From: Sebastian Schuberth <sschuberth@gmail.com>
To: git@vger.kernel.org
Subject: What is an efficient way to get all blobs / trees that have notes attached?
Date: Fri, 1 Apr 2016 12:51:52 +0200 [thread overview]
Message-ID: <ndljs8$vj3$1@ger.gmane.org> (raw)
Hi,
I'm curious whether there's a more efficient way to get a list of blobs
/ trees (and their names) that have notes attached than doing this:
1) Get all notes refs I'm interested in (git-for-each-ref).
2) For each notes ref, get the list of notes (git-notes list) and store
them in a hash table that maps object hashes to notes.
3) Recursively list all blobs / trees (git-ls-tree) and look whether an
object's hash is conatined in our table to get its notes.
In particular 3) could be expensive for repos with a lot of files as
we're looking at all of them just to see whether they have notes attached.
Regards,
Sebastian
next reply other threads:[~2016-04-01 10:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 10:51 Sebastian Schuberth [this message]
2016-04-01 12:16 ` What is an efficient way to get all blobs / trees that have notes attached? Johan Herland
2016-04-01 12:23 ` Johan Herland
2016-04-04 7:46 ` Sebastian Schuberth
2016-04-04 17:33 ` 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='ndljs8$vj3$1@ger.gmane.org' \
--to=sschuberth@gmail.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).