From: Noam Postavsky <npostavs@users.sourceforge.net>
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 09:59:22 -0500 [thread overview]
Message-ID: <CAM-tV-9QPXb7WdTQ-mA6HB7gFnwvynEjNVewNApbqu3WuHYpLw@mail.gmail.com> (raw)
In-Reply-To: <87shcvdf27.fsf@gmx.net>
On Thu, Nov 30, 2017 at 9:19 AM, Stephen Berman <stephen.berman@gmx.net> wrote:
> I'm not sure what you mean by "reachable from a branch"; what I want is
> to find out whether a specific commit (identified by its hash) exists on
> the current branch -- not just whether it exists on some branch in the
> current repository -- and if so, to see that commit.
git doesn't really have branches like you are talking about, it just
has movable tags.
> 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, but it appears unable to say which branch it's on.
'git log <commit>' means "show all commits starting with <commit>
going backwards".
'git log' is just a short form for 'git log HEAD' (i.e., the commit
you are currently on).
next prev parent reply other threads:[~2017-11-30 14:59 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 [this message]
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
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=CAM-tV-9QPXb7WdTQ-mA6HB7gFnwvynEjNVewNApbqu3WuHYpLw@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--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).