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

Re: Merge without marking conflicts in working tree

From
Andreas Schwab <schwab@linux-m68k.org>
Date
Nov 17, 2014, 23:20 UTC
Message-ID
<87sihhza6a.fsf@igel.home>
In-Reply-To
<20141117223836.GH615@pug.qqx.org>
Aaron Schrab <aaron@schrab.com> writes:
Show 9 quoted lines
> Is there a way to do a merge but only record conflicts in the index, not
> update the working versions of files with conflict markers?
>
> Like many people, I use git to manage configuration files for my shell,
> editor, git itself, and a number of other things.  The vast majority of
> times that I update things no conflicts are occur and everything just
> works, so I'd like to avoid extra work in this case.  But occasionally a
> conflict will occur, and if it's in a file that will be read while trying
> to resolve the conflict this can make things more difficult.

You could perform the merge in a separate working directory. The only extra step required is a checkout to deploy the new revision, which could be triggered automatically by a hook.

Andreas.
-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
Previous: Junio C Hamano
Message 3 of 3 in “Merge without marking conflicts in working tree”
  1. Aaron SchrabNov 17, 2014
  2. Junio C HamanoNov 17, 2014
  3. Andreas SchwabNov 17, 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.