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

Re: [RFC/PATCH] git-merge: implement --ff-only-merge option.

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 7, 2014, 20:27 UTC
Message-ID
<xmqqegujeibx.fsf@gitster.dls.corp.google.com>
In-Reply-To
<87fvezsk5k.fsf@osv.gnss.ru>
Sergey Organov <sorganov@gmail.com> writes:
Show 6 quoted lines
>> Why would it be useful to limit the history to a shape where all
>> merges are the ones that could have been fast-forwarded?
>
> Except by true merge, how else can I express with git that 'n'
> consequitive commits constitute single logical change (being originally
> some topic branch)?
You are justifying --no-ff, aren't you?
> Moreover, as topic branches are usually rebased before merge anyway,
> why shouldn't I have simple capability to enforce it?

Because rebasing immediately before is considered a bad manner, i.e. encouraging a wrong workflow?

Previous: Sergey OrganovNext: Sergey Organov
Message 4 of 7 in “git-merge: implement --ff-only-merge option.”
  1. git-merge: implement --ff-only-merge option.Sergey Organov, Oct 7, 2014
  2. Junio C HamanoOct 7, 2014
  3. Sergey OrganovOct 7, 2014
  4. Junio C HamanoOct 7, 2014
  5. Sergey OrganovOct 7, 2014
  6. Junio C HamanoOct 7, 2014
  7. Sergey OrganovOct 8, 2014

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.