From: David Kastrup <dak@gnu.org>
To: git@vger.kernel.org
Subject: A question about git-rev-list
Date: Mon, 16 Jul 2007 10:55:35 +0200 [thread overview]
Message-ID: <86wsx0wwvs.fsf@lola.quinscape.zz> (raw)
Hi,
if I do
git-rev-list --remove-empty HEAD --not some-commit -- filename | tail -1
do I have any guarantee that the commit id I get (if any) is a direct
descendant of some-commit? I _think_ --remove-empty might be
necessary for that option, but have no idea whether this hunch is
correct. Do I need additional options like --topo-order, or is that
unnecessary?
Thanks,
--
David Kastrup
next reply other threads:[~2007-07-16 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 8:55 David Kastrup [this message]
2007-07-16 20:05 ` A question about git-rev-list Linus Torvalds
2007-07-16 21:16 ` David Kastrup
2007-07-17 4:33 ` Junio C Hamano
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=86wsx0wwvs.fsf@lola.quinscape.zz \
--to=dak@gnu.org \
--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