From: Andreas Schwab <schwab@linux-m68k.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: Mathias Megyei <mathias@mnet-mail.de>,
Emacs developers <emacs-devel@gnu.org>,
Yuri Khan <yuri.v.khan@gmail.com>
Subject: Re: git log question
Date: Thu, 30 Nov 2017 16:05:48 +0100 [thread overview]
Message-ID: <87efofrelv.fsf@linux-m68k.org> (raw)
In-Reply-To: <87shcvdf27.fsf@gmx.net> (Stephen Berman's message of "Thu, 30 Nov 2017 15:19:44 +0100")
On Nov 30 2017, Stephen Berman <stephen.berman@gmx.net> wrote:
> Thanks, but this does do what I want. For example, when I invoke `git
> branch --contains b407c521f2' on emacs-26 (here currently at
> 408862f02a), it outputs `master', but when I invoke `git merge-base
> --is-ancestor b407c521f2 HEAD && git log -1 b407c521f2' on emacs-26, it
> outputs nothing;
That's correct, b407c521f2 is only reachable from master. So this is
exactly what you were looking for.
> That is, `git log' invoked with a specific commit will find that commit
Git lets you process any valid commit in your repository. That's a
feature. All commits in your repository are alike, no matter how they
are named.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2017-11-30 15:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 10:00 git log question Stephen Berman
2017-11-30 11:30 ` Mathias Megyei
2017-11-30 12:02 ` Stephen Berman
2017-11-30 13:15 ` Yuri Khan
2017-11-30 14:19 ` Stephen Berman
2017-11-30 14:59 ` Noam Postavsky
2017-11-30 15:05 ` Yuri Khan
2017-11-30 15:05 ` Andreas Schwab [this message]
2017-11-30 15:21 ` Kaushal Modi
2017-11-30 15:25 ` Andreas Schwab
2017-11-30 15:35 ` Noam Postavsky
2017-11-30 17:46 ` Clément Pit-Claudel
2017-11-30 17:59 ` Kaushal Modi
2017-11-30 17:06 ` Davis Herring
2017-11-30 19:11 ` Stephen Berman
2017-11-30 14:28 ` Herring, Davis
2017-11-30 14:37 ` Stephen Berman
2017-11-30 15:57 ` Eli Zaretskii
2017-11-30 19:10 ` Stephen Berman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87efofrelv.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=emacs-devel@gnu.org \
--cc=mathias@mnet-mail.de \
--cc=stephen.berman@gmx.net \
--cc=yuri.v.khan@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).