From: Jonas Gehring <jonas.gehring@boolsoft.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH/RFC] Implemented return value for rev-list --quiet
Date: Wed, 27 Apr 2011 01:31:30 +0200 [thread overview]
Message-ID: <4DB755D2.10303@boolsoft.org> (raw)
In-Reply-To: <7vwrigbor6.fsf@alter.siamese.dyndns.org>
On 04/27/2011 01:02 AM, Junio C Hamano wrote:
> Given two commits A and X, "rev-list --objects A..X" is a way to make sure
> that everything between A and X exists.
Thank you for this explanation, this really cleared up the intended
usage of --quiet for me. I wanted to use it for ancestry testing of two
commits, noticed the hard-coded return value of '0' in cmd_rev_list()
and thought that the implementation is probably missing.
After some additional digging, I realized that git-merge-base is the
right tool for my task.
Regards,
Jonas
next prev parent reply other threads:[~2011-04-26 23:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 22:36 [PATCH/RFC] Implemented return value for rev-list --quiet Jonas Gehring
2011-04-26 23:02 ` Junio C Hamano
2011-04-26 23:31 ` Jonas Gehring [this message]
2011-04-26 23:47 ` 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=4DB755D2.10303@boolsoft.org \
--to=jonas.gehring@boolsoft.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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).