git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Wild <themiwi@users.sourceforge.net>
To: git@vger.kernel.org
Subject: conflict status
Date: Mon, 3 Aug 2009 17:14:00 +0200	[thread overview]
Message-ID: <DDAD985F-C9CA-4159-B382-354D4B082C19@users.sourceforge.net> (raw)

Hi all

I'm merging two branches with a large number of conflicts.  
Fortunately, there are many modified/deleted conflicts (locally  
modified, remotely deleted), and I know that for those I want to pick  
the deleted version. However, I can't seem to motivate GIT into  
telling me for which of the conflicting files this is the case. I know  
that git-mergetool somehow extracts this information, but looking at  
the code, it seems to me that there must be an easier, user-level  
method of obtaining this information.

Generally speaking, I would like to know for each file with a conflict  
what it's status is, similar to what SVN does:
- locally modified/created/deleted/...
- remotely modified/created/deleted/...

Please excuse me if this is either trivial or has been answered many  
times before, but neither perusing the man-pages, nor asking google  
turned up anything remotely useful.

Thanks for the help

Michael

             reply	other threads:[~2009-08-03 16:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-03 15:14 Michael Wild [this message]
2009-08-03 17:37 ` conflict status Sverre Rabbelier
2009-08-03 18:17   ` Thomas Rast
2009-08-03 18:35     ` Junio C Hamano
2009-08-04  7:10       ` Michael Wild
2009-08-04  7:19         ` Jakub Narebski
2009-08-04  7:31           ` Michael Wild
2009-08-04  7:56         ` Junio C Hamano

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=DDAD985F-C9CA-4159-B382-354D4B082C19@users.sourceforge.net \
    --to=themiwi@users.sourceforge.net \
    --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 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).