From: Junio C Hamano <gitster@pobox.com>
To: Han Jiang <jhcarl0814@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: `git log FETCH_HEAD` only logs whatever happens to be the first among the fetched refs (instead of all the fetched refs)
Date: Thu, 05 Sep 2024 08:01:20 -0700 [thread overview]
Message-ID: <xmqqplpi5em7.fsf@gitster.g> (raw)
In-Reply-To: <CANrWfmSMbR+8oGsCzOygBA0sFSmMwUmCy=qQEsa16RWcztYaQA@mail.gmail.com> (Han Jiang's message of "Thu, 5 Sep 2024 16:25:50 +1200")
This is totally expected. FETCH_HEAD is only special to "git
merge". When FETCH_HEAD is used as if it were a ref, everybody else
uses only the first entry.
next prev parent reply other threads:[~2024-09-05 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 4:25 `git log FETCH_HEAD` only logs whatever happens to be the first among the fetched refs (instead of all the fetched refs) Han Jiang
2024-09-05 15:01 ` Junio C Hamano [this message]
2024-09-05 22:17 ` Han Jiang
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqplpi5em7.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jhcarl0814@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.