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

Re: FW: question about merge in 1.7.10

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 24, 2012, 20:00 UTC
Message-ID
<7vobsoypb3.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1F026B57884A5841B330471696849DE9114503D7@MBX021-W4-CA-5.exch021.domain.local>
Marlene Cote <Marlene_Cote@affirmednetworks.com> writes:
> I used merge with -no-commit -no-ff. So, I assume I won't see any
> change in behavior, since merge is not performing commits, right?
The _only_ difference is when
 (1) "git merge" is run interactively;
 (2) the merge goes cleanly that it does not need to ask help from the
     user to resolve conflicts; and
 (3) it records the result by creating a commit.

Because your use case with "--no-commit" does not satisfy the last criteria, I do not expect you to see any difference. Otherwise you may have found a bug.

As noted in
    http://git-blame.blogspot.com/2012/02/anticipating-git-1710.html

please try out the version from the 'master' branch before it gets released, so that you can help us avoid surprises in the corner cases.

Thanks.
Previous: Junio C Hamano
Message 7 of 7 in “FW: question about merge in 1.7.10”
  1. Marlene CoteFeb 24, 2012
  2. Zbigniew Jędrzejewski-SzmekFeb 24, 2012
  3. Marlene CoteFeb 24, 2012
  4. Junio C HamanoFeb 24, 2012
  5. Marlene CoteFeb 24, 2012
  6. Junio C HamanoFeb 24, 2012
  7. Junio C HamanoFeb 24, 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.