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

Re: [PATCH] Also read SQUASH_MSG if a conflict on a merge squash occurred

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 9, 2016, 18:04 UTC
Message-ID
<xmqqfuvzil3y.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<xmqq60wwlt0s.fsf@gitster.mtv.corp.google.com>
Junio C Hamano <gitster@pobox.com> writes:
Show 17 quoted lines
> The duplicated code to read the same file bothers me somewhat.
>
> I wondered if it makes the result easier to follow (and easier to
> update) if this part of the code is restructured like this:
>
> 	if (file_exists(git_path_merge_msg()) ||
>             file_exists(git_path_squash_msg())) {
> 	    if (file_exists(git_path_squash_msg())) {
> 		read SQUASH_MSG;
> 	    }
>             if (file_exists(git_path_merge_msg()))
>             	read MERGE_MSG;
> 	    }
>             hook_arg1 = "merge";
> 	}
>
> but I am not sure if that structure is better.

... as this duplicates file_exists() call to the same thing, which is no better than duplicated calls to read *_MSG files.

Previous: Sven StrickrothNext: Junio C Hamano
Message 7 of 13 in “Commit message not helpful after merge squash with conflicts”
  1. Sven StrickrothMar 5, 2016
  2. Also read SQUASH_MSG if a conflict on a merge squash occurredSven Strickroth, Mar 8, 2016
  3. Junio C HamanoMar 8, 2016
  4. Sven StrickrothMar 8, 2016
  5. Junio C HamanoMar 8, 2016
  6. commit: do not lose SQUASH_MSG contentsSven Strickroth, Mar 8, 2016
  7. Junio C HamanoMar 9, 2016
  8. Junio C HamanoMar 9, 2016
  9. commit: do not lose SQUASH_MSG contentsSven Strickroth, Mar 13, 2016
  10. Junio C HamanoMar 14, 2016
  11. Junio C HamanoMar 14, 2016
  12. commit: do not lose SQUASH_MSG contentsSven Strickroth, Mar 21, 2016
  13. Junio C HamanoMar 21, 2016

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.