Re: [PATCH] merge: --ff-one-only to apply FF if commit is one

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

Subject: Re: [PATCH] merge: --ff-one-only to apply FF if commit is one
From: Junio C Hamano <gitster@xxxxxxxxx>
Date: Tue, 31 Oct 2023 15:07:50 +0900
Cc: git@xxxxxxxxxxxxxxx
In-reply-to: <9f584927-7506-421e-a363-953eebb0ef90@gmail.com> (Ruslan Yakauleu's message of "Tue, 31 Oct 2023 08:48:40 +0300")
References: <pull.1599.git.git.1698224280816.gitgitgadget@gmail.com> <ZUALkdSJZ70+KBYq@nand.local> <xmqq1qdb8wzk.fsf@gitster.g> <9f584927-7506-421e-a363-953eebb0ef90@gmail.com>
User-agent: Gnus/5.13 (Gnus v5.13)

Ruslan Yakauleu <ruslan.yakauleu@xxxxxxxxx> writes:

> Command of developers can decide which policy use and why.
> If a team decides to avoid extra merges - why not?

I never said "--ff" is a bad option that should not exist, and I am
not sure why I had to be thrown such a rhetorical question at.

References:
- [PATCH] merge: --ff-one-only to apply FF if commit is one
  - From: Ruslan Yakauleu via GitGitGadget
- Re: [PATCH] merge: --ff-one-only to apply FF if commit is one
  - From: Taylor Blau
- Re: [PATCH] merge: --ff-one-only to apply FF if commit is one
  - From: Junio C Hamano
- Re: [PATCH] merge: --ff-one-only to apply FF if commit is one
  - From: Ruslan Yakauleu

Prev by Date: Re: [PATCH 0/3] Add `-p' option to `git-mv', inspired by `mkdir'
Next by Date: Re: [PATCH] merge: --ff-one-only to apply FF if commit is one
Previous by thread: Re: [PATCH] merge: --ff-one-only to apply FF if commit is one
Next by thread: Re: [PATCH] merge: --ff-one-only to apply FF if commit is one
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