Why isn't 'jch' based on 'next'?

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

Subject: Why isn't 'jch' based on 'next'?
From: Denton Liu <liu.denton@xxxxxxxxx>
Date: Thu, 15 Apr 2021 02:12:02 -0700
Cc: git@xxxxxxxxxxxxxxx

Hi Junio,

Out of curiosity, why is 'jch' not based on 'next' but instead, it
recreates the same merge commits on top of 'master'. What is the
advantage of this?

Thanks,
Denton

Follow-Ups:
- Re: Why isn't 'jch' based on 'next'?
  - From: Junio C Hamano

Prev by Date: Re: [PATCH 2/2] repack: avoid loosening promisor pack objects in partial clones
Next by Date: Re: [PATCH 0/2] prevent `repack` to unpack and delete promisor objects
Previous by thread: possible bug due to directory rename detection
Next by thread: Re: Why isn't 'jch' based on 'next'?
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