git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Detect merge/rebase conflicts without changing the worktree?
@ 2010-10-27 23:40 Klas Lindberg
  2010-10-28  0:01 ` Jonathan Nieder
  0 siblings, 1 reply; 3+ messages in thread
From: Klas Lindberg @ 2010-10-27 23:40 UTC (permalink / raw)
  To: git

Hello

What is the recommended way to detect merge/rebase conflicts without
actually modifying the worktree? Should I use some combination of
custom $GIT_INDEX_FILE and --work-tree to lock the conflict resolution
into a directory specially made for this purpose? Is there even a way
to have the conflict-annotated files written to stdout instead of to
file system when a merge fails?

BR / Klas

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-10-28 10:01 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-10-27 23:40 Detect merge/rebase conflicts without changing the worktree? Klas Lindberg
2010-10-28  0:01 ` Jonathan Nieder
2010-10-28 10:01   ` Klas Lindberg

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).