From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: git log question
Date: Thu, 30 Nov 2017 20:10:33 +0100 [thread overview]
Message-ID: <87bmjjd1li.fsf@gmx.net> (raw)
In-Reply-To: <83y3mn3gjc.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 30 Nov 2017 17:57:59 +0200")
On Thu, 30 Nov 2017 17:57:59 +0200 Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Stephen Berman <stephen.berman@gmx.net>
>> Date: Thu, 30 Nov 2017 11:00:54 +0100
>>
>> I thought if I call `git log <commit> -1' on the current branch, it will
>> only show <commit> if it is in the current branch, but I just discovered
>> this is not so: I called it with master current and <commit> being one I
>> knew was only in emacs-26, but nevertheless it showed that commit.
>
> Isn't that because we merge from emacs-26 to master, and that commit
> was merged as part of that?
No, this was prior to that commit being merged to master (cf. my example
of a commit existing only on master but being shown when invoking `git
log <commit>' on emacs-26).
Steve Berman
prev parent reply other threads:[~2017-11-30 19:10 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
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 [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
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=87bmjjd1li.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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).