From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: git-rev-list --full-history --parents doesn't respect path limit and shows all merges
Date: Wed, 06 Sep 2006 13:11:12 +0200 [thread overview]
Message-ID: <edmabt$3tc$1@sea.gmane.org> (raw)
When trying to speed-up gitweb by using only one git-rev-list invocation to
get _parsed_ list of revisions, and not first call git-rev-list to get list
of revisions, and then for each revision call git-rev-list --max-count=1
--parennts --header to parse a commit, I have encountered the following
error in (most probably) --full-history implementation.
Namely the following work as expected, returning only one commit:
git rev-list HEAD -- gitweb/git-logo.png
git rev-list HEAD --full-history -- gitweb/git-logo.png
git rev-list HEAD --parents -- gitweb/git-logo.png
but the following command
git rev-list HEAD --full-history --parents -- gitweb/git-logo.png
returns additionally _all_ the merges.
I don't know if it is a feature or a bug (I think that is the latter),
but it seriously screw mentioned plan to make gitweb faster a bit.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
reply other threads:[~2006-09-06 11:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='edmabt$3tc$1@sea.gmane.org' \
--to=jnareb@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).