git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Merge option suggestion (dictator, humble)

From
Andrew Ardill <andrew.ardill@gmail.com>
Date
Oct 16, 2012, 23:17 UTC
Message-ID
<CAH5451me=JC5kL-_LZNaSrEX3b1MR6W6sa=A8CUtsxH480wm3g@mail.gmail.com>
In-Reply-To
<7vpq4is553.fsf@alter.siamese.dyndns.org>
On 17 October 2012 04:23, Junio C Hamano <gitster@pobox.com> wrote:
Show 16 quoted lines
> 乙酸鋰 <ch3cooli@gmail.com> writes:
>
>> I would like to suggest 2 merge options
>> --dictator   use all my changes
>> --humble   use all their changes
>>
>> These allows to produce a fast-forward commit, without resolving any conflicts.
>> Sometimes, someone did something completely wrong, so the commit needs
>> to be ignored.
>
>> I cannot tell everyone in the world to run git fetch followed by git
>> reset --hard.
>
> Then you cannot tell them to use "pull --humble" either, can you?
>
> Not seeing any merit in the proposal (yet).

Would this allow setting up a project-default merge configuration for contributors that defaulted to --humble? Not sure if that is useful or not, but it at least seems safer than trying to default to doing reset --hard after every merge.

Regards,
Andrew Ardill
Previous: Junio C Hamano
Message 3 of 3 in “Merge option suggestion (dictator, humble)”
  1. 乙酸鋰Oct 16, 2012
  2. Junio C HamanoOct 16, 2012
  3. Andrew ArdillOct 16, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.