From: Aaron Schrab <aaron@schrab.com>
To: git@vger.kernel.org
Subject: Merge without marking conflicts in working tree
Date: Mon, 17 Nov 2014 17:38:36 -0500 [thread overview]
Message-ID: <20141117223836.GH615@pug.qqx.org> (raw)
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.
I'd like to find a way to have the conflict recorded in just the index
without touching the working tree. I could then use my usual tools to
resolve the conflict without the errors caused by the conflict markers.
I generally use vim+fugitive to resolve conflicts anyway, and typically
the first step I take is to replace the working-tree version with the
merge-base version, completely ignoring any conflict markers.
If there isn't currently a way to do this, I was thinking of
implementing something like an "ours" value for merge.conflictstyle
configuration.
next reply other threads:[~2014-11-17 22:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 22:38 Aaron Schrab [this message]
2014-11-17 23:19 ` Merge without marking conflicts in working tree Junio C Hamano
2014-11-17 23:20 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141117223836.GH615@pug.qqx.org \
--to=aaron@schrab.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.