Re: `git log FETCH_HEAD` only logs whatever happens to be the first among the fetched refs (instead of all the fetched refs)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: `git log FETCH_HEAD` only logs whatever happens to be the first among the fetched refs (instead of all the fetched refs)
From: Junio C Hamano <gitster@xxxxxxxxx>
Date: Thu, 05 Sep 2024 08:01:20 -0700
Cc: Git Mailing List <git@xxxxxxxxxxxxxxx>
In-reply-to: <CANrWfmSMbR+8oGsCzOygBA0sFSmMwUmCy=qQEsa16RWcztYaQA@mail.gmail.com> (Han Jiang's message of "Thu, 5 Sep 2024 16:25:50 +1200")
References: <CANrWfmSMbR+8oGsCzOygBA0sFSmMwUmCy=qQEsa16RWcztYaQA@mail.gmail.com>
User-agent: Gnus/5.13 (Gnus v5.13)

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.

Follow-Ups:
- Re: `git log FETCH_HEAD` only logs whatever happens to be the first among the fetched refs (instead of all the fetched refs)
  - From: Han Jiang

References:
- `git log FETCH_HEAD` only logs whatever happens to be the first among the fetched refs (instead of all the fetched refs)
  - From: Han Jiang

Prev by Date: Re: [PATCH v4 1/6] t: move reftable/stack_test.c to the unit testing framework
Next by Date: [PATCH v2 0/4] hash.h: support choosing a separate SHA-1 for non-cryptographic uses
Previous by thread: `git log FETCH_HEAD` only logs whatever happens to be the first among the fetched refs (instead of all the fetched refs)
Next by thread: Re: `git log FETCH_HEAD` only logs whatever happens to be the first among the fetched refs (instead of all the fetched refs)
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]

Powered by Linux