From: Jakub Narebski <jnareb@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>,
"Derrick Stolee" <stolee@gmail.com>,
"Karl Ostmo" <kostmo@gmail.com>,
git@vger.kernel.org
Subject: Re: standalone library/tool to query commit-graph?
Date: Tue, 25 Jun 2019 20:27:32 +0200 [thread overview]
Message-ID: <86ftnx4j1n.fsf@gmail.com> (raw)
In-Reply-To: <87o93sfahj.fsf@evledraar.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Fri, 24 May 2019 11:49:28 +0200")
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
[...]
> To clarify (and I should have said) I meant it'll include only packed
> commits in the mode Karl Ostmo invoked it in, as Derrick points out.
>
> But yeah, you can of course give it arbitrary starting points, but
> needing to deal with those sorts of caveats makes it rather useless in
> practice for the sort of use-case Jakub mused about, but more
> importantly a full XML dump of the graph isn't going to get much of a
> benefit from the commit graph, it helps with algorithms that want to
> avoid those sorts of full walks.
Actually for an "XML dump" of a graph of revisions (assuming that you
can give nodes and edges in arbitrary order in this graph output format)
doing it using serialized commit-graph should be faster: you only need
to read one file, and convert it to other format (perhaps even in a
streaming manner). No need to delta-unpack, decompress and parse commit
objects.
Though on the other hand you are right: if "git log --graph" uses
serialized commit graph, and it is used for XML / JSON dump, it should
also be fast. If there is no serialized commit graph, you still can
generate XML dump.
Best,
--
Jakub Narębski
prev parent reply other threads:[~2019-06-25 18:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 18:49 standalone library/tool to query commit-graph? Karl Ostmo
2019-05-22 18:59 ` Derrick Stolee
2019-05-23 19:29 ` Jakub Narebski
2019-05-23 21:54 ` Ævar Arnfjörð Bjarmason
2019-05-23 22:20 ` SZEDER Gábor
2019-05-23 23:48 ` Derrick Stolee
2019-05-24 9:34 ` SZEDER Gábor
2019-05-24 9:49 ` Ævar Arnfjörð Bjarmason
2019-05-24 10:06 ` SZEDER Gábor
2019-05-24 10:49 ` Ævar Arnfjörð Bjarmason
2019-05-24 11:37 ` SZEDER Gábor
2019-06-25 18:27 ` Jakub Narebski [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=86ftnx4j1n.fsf@gmail.com \
--to=jnareb@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=kostmo@gmail.com \
--cc=stolee@gmail.com \
--cc=szeder.dev@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.