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

Re: merge ignores --no-commit in fast-forward case

From
Paolo Bonzini <bonzini@gnu.org>
Date
Sep 20, 2009, 14:04 UTC
Message-ID
<4AB63678.6010500@gnu.org>
In-Reply-To
<7viqff97l4.fsf@alter.siamese.dyndns.org>
On 09/19/2009 01:05 AM, Junio C Hamano wrote:
Show 5 quoted lines
> If "surprising" is the problem (and it certainly is), perhaps it would be
> better to rewrite it not to be so surprising, like:
>
>          --no-commit::
>                  Do not create a new commit.
Do not create a new _merge_ commit, and it's perfect.
Paolo
Previous: Junio C HamanoNext: Björn Steinbrink
Message 5 of 6 in “merge ignores --no-commit in fast-forward case”
  1. Tomas CarneckySep 13, 2009
  2. Junio C HamanoSep 13, 2009
  3. Greg PriceSep 18, 2009
  4. Junio C HamanoSep 18, 2009
  5. Paolo BonziniSep 20, 2009
  6. Björn SteinbrinkSep 19, 2009

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.