git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Caleb Cushing <xenoterracide@gmail.com>
To: git@vger.kernel.org
Subject: mergetool feature request - select remote or local
Date: Wed, 14 May 2008 07:21:00 -0400	[thread overview]
Message-ID: <200805140721.13719.xenoterracide@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 860 bytes --]

sometimes when merge-ing fast forward doesn't work. but you know what the 
resolution you want is.

example (current behavior)
Normal merge conflict for 'css/main.css':
  {local}: modified
  {remote}: modified
Hit return to start merge resolution tool (vimdiff):

but I don't want to. I know the remote updates are right. I could do a git 
checkout remotebranch filename but when you have 20 files that need updating 
this is annoying

my suggestion is this
Normal merge conflict for 'css/main.css':
  {local}: modified
  {remote}: modified
Use (l)local or (r)remote or (m)anual? 

also in the event of having 20 files with this issue it would be nice to have 
an option after first starting mergetool for remote all or local all.

(note: I am not subscribed to the list)
-- 
Caleb Cushing

my blog http://xenoterracide.blogspot.com

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2008-05-14 11:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14 11:21 Caleb Cushing [this message]
2008-05-14 17:47 ` mergetool feature request - select remote or local Junio C Hamano
2008-05-14 18:40   ` Daniel Barkalow
2008-05-14 19:19     ` Junio C Hamano
2008-05-15  1:25   ` Caleb Cushing

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=200805140721.13719.xenoterracide@gmail.com \
    --to=xenoterracide@gmail.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 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).