[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: git log question
From: |
Andreas Schwab |
Subject: |
Re: git log question |
Date: |
Thu, 30 Nov 2017 16:05:48 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.0.90 (gnu/linux) |
On Nov 30 2017, Stephen Berman <address@hidden> 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, address@hidden
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
- git log question, Stephen Berman, 2017/11/30
- Re: git log question, Mathias Megyei, 2017/11/30
- Re: git log question, Stephen Berman, 2017/11/30
- Re: git log question, Yuri Khan, 2017/11/30
- Re: git log question, Stephen Berman, 2017/11/30
- Re: git log question, Noam Postavsky, 2017/11/30
- Re: git log question, Yuri Khan, 2017/11/30
- Re: git log question,
Andreas Schwab <=
- Re: git log question, Kaushal Modi, 2017/11/30
- Re: git log question, Andreas Schwab, 2017/11/30
- Re: git log question, Noam Postavsky, 2017/11/30
- Re: git log question, Davis Herring, 2017/11/30
Re: git log question, Herring, Davis, 2017/11/30
Re: git log question, Eli Zaretskii, 2017/11/30