From: Davis Herring <herring@lanl.gov>
To: Stephen Berman <stephen.berman@gmx.net>,
Yuri Khan <yuri.v.khan@gmail.com>
Cc: Mathias Megyei <mathias@mnet-mail.de>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: git log question
Date: Thu, 30 Nov 2017 10:06:00 -0700 [thread overview]
Message-ID: <24a86127-902e-fa6e-cc64-154a6e6487e4@lanl.gov> (raw)
In-Reply-To: <87shcvdf27.fsf@gmx.net>
(All these commands have been given by others in this thread; this
message aims to better relate them to the questions asked.)
> I find the following puzzling:
>
> steve [ ~/git/emacs-master ]$ git log --oneline | grep b407c521f2
> b407c521f2 Remove pinentry.el
>
> steve [ ~/git/emacs-26 ]$ git log --oneline | grep b407c521f2
>
> The latter gives no output; yet:
This command of course answers your original question: "Is commit C on
branch B?". You could use "grep -q" to make it a test, but "git
merge-base --is-ancestor C B" is more efficient.
> steve [ ~/git/emacs-26 ]$ git log --oneline b407c521f2 -1
> b407c521f2 Remove pinentry.el
>
> That is, `git log' invoked with a specific commit will find that commit
> even when it's not on the current branch but on another branch in this
> repository,
"git log" == "git log HEAD"; "git log X" reports X itself and all
commits in its history.
> but it appears unable to say which branch it's on.
This is a different, dual question: "Which branches contain commit C?",
for which the command is "git branch [-r|-a] --contains C".
Davis
--
This product is sold by volume, not by mass. If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.
next prev parent reply other threads:[~2017-11-30 17:06 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
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 [this message]
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=24a86127-902e-fa6e-cc64-154a6e6487e4@lanl.gov \
--to=herring@lanl.gov \
--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).