Marc Branchaud writes:
> The docs say that all the fetched refs are written to FETCH_HEAD (perhaps a
> more accurate name would have been FETCH_HEADS?). If that's truly the case,
> it seems weird to use FETCH_HEAD in log and merge commands. (My FETCH_HEAD
> file currently has 1434 lines in it -
On 14-05-30 01:52 PM, Junio C Hamano wrote:
> Marc Branchaud writes:
>
>> On 14-05-29 06:42 PM, Junio C Hamano wrote:
>>> +
>>> +The names of refs that are fetched, together with the object names
>>> +they point at, are written to `.git/FETCH_HEAD`. This information
>>> +is used by a later merge
Marc Branchaud writes:
> On 14-05-29 06:42 PM, Junio C Hamano wrote:
>> - "Branches" is a more common way to say "heads" in these days.
>>
>> - Remote-tracking branches are used a lot more these days and it is
>>worth mentioning that it is one of the primary side effects of
>>the comma
On 14-05-29 06:42 PM, Junio C Hamano wrote:
> - "Branches" is a more common way to say "heads" in these days.
>
> - Remote-tracking branches are used a lot more these days and it is
>worth mentioning that it is one of the primary side effects of
>the command to update them.
>
> - Avoid
4 matches
Mail list logo
