From: Brian Foster <brian.foster@maxim-ic•com>
To: Junio C Hamano <gitster@pobox•com>
Cc: git mailing list <git@vger•kernel.org>,
Sitaram Chamarty <sitaramc@gmail•com>
Subject: Re: [Q] Determing if a commit is reachable from the HEAD ?
Date: Tue, 24 Jan 2012 09:56:15 +0100 [thread overview]
Message-ID: <201201240956.15624.brian.foster@maxim-ic.com> (raw)
In-Reply-To: <7vk44i9z99.fsf@alter.siamese.dyndns.org>
On Monday 23 January 2012 17:09:38 Junio C Hamano wrote:
> Brian Foster <brian.foster@maxim-ic•com> writes:
> > I am probably misunderstanding ‘--quiet’, which the
> > man page cryptically describes as “... allow the
> > caller to test the exit status to see if a range
> > of objects is fully connected (or not).” What is
> > meant here by “fully connected” ?
>
> If the real history looks like this:
>
> ---Y---x---HEAD
>
> i.e. the commit at HEAD says "parent x" in it, and your [repository]
> lacks "x" for whatever reason, Y..HEAD is not fully connected.
Ah, Ok. Thanks! Then YES, I misunderstood ‘--quiet’.
The man page caused me to think it was functionally
equivalent to ‘git rev-list STUFF >/dev/null’.
cheers!
-blf-
--
Brian Foster
Principal MTS, Software | La Ciotat, France
Maxim Integrated Products | Web: http://www.maxim-ic.com/
prev parent reply other threads:[~2012-01-24 8:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 13:33 [Q] Determing if a commit is reachable from the HEAD ? Brian Foster
2012-01-20 14:13 ` Andreas Schwab
2012-01-20 18:06 ` David Brown
2012-01-20 19:18 ` Junio C Hamano
2012-01-20 23:33 ` David Brown
2012-01-21 0:04 ` Junio C Hamano
2012-01-21 4:58 ` David Brown
2012-01-20 22:50 ` Sitaram Chamarty
2012-01-23 9:20 ` Brian Foster
2012-01-23 16:09 ` Junio C Hamano
2012-01-24 8:16 ` Brian Foster
2012-01-24 8:56 ` Brian Foster [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=201201240956.15624.brian.foster@maxim-ic.com \
--to=brian.foster@maxim-ic$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=sitaramc@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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