All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: Caleb Cushing <xenoterracide@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: more merge strategies : feature request
Date: Mon, 01 Dec 2008 10:18:59 +0100	[thread overview]
Message-ID: <4933AC03.6050300@op5.se> (raw)
In-Reply-To: <81bfc67a0811290848m6cb219c0y71a7266001096f2d@mail.gmail.com>

Caleb Cushing wrote:
> conflict: this strategy would always resolve in a merge conflict
> allowing you to use git mergetool to piece the files back together.
> 
> no-overwrite: if a change from the branch being merged in would
> overwrite something in the current branch don't merge it. (I think it
> needs a better name)
> 

If you could come up with use-cases where each would be useful, I
think you'd have a much easier time to gain acceptance for your
suggestions. Right now, you're saying "I want a red button" but
you're not explaining what it's for.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

  reply	other threads:[~2008-12-01  9:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-29 16:48 more merge strategies : feature request Caleb Cushing
2008-12-01  9:18 ` Andreas Ericsson [this message]
2008-12-02  2:38   ` Caleb Cushing
2008-12-02  3:30     ` Jeff King
2008-12-02 14:28       ` Caleb Cushing
2008-12-02 15:30         ` Jeff King
2008-12-02  2:49   ` Leo Razoumov
2008-12-02 13:46     ` Caleb Cushing
2008-12-03  1:07       ` Leo Razoumov
2008-12-03 21:27         ` Nanako Shiraishi
2008-12-03 22:59           ` Caleb Cushing
2008-12-04  2:15           ` Junio C Hamano
2008-12-04 10:11             ` Nanako Shiraishi

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=4933AC03.6050300@op5.se \
    --to=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=xenoterracide@gmail.com \
    /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.