From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"David Lang" <david.lang@digitalinsight.com>,
git@vger.kernel.org
Subject: Re: merge strategy request
Date: Mon, 26 Mar 2007 11:34:29 +1200 [thread overview]
Message-ID: <46a038f90703251634t2ab6a455t382ebe29cdb53667@mail.gmail.com> (raw)
In-Reply-To: <7v648paj14.fsf@assigned-by-dhcp.cox.net>
On 3/25/07, Junio C Hamano <junkio@cox.net> wrote:
> Right. In the current system, git-mergetool might be a better
> place to add support for special perpose 3-version file-level
> merge backend than merge-recursive, at least until gitattributes
> materializes.
Would it be possible to have an env var (GIT_MERGE) that can be used
to call an arbitrary script with merge/diff3 semantics instead of
using the internal 3-way merge? That way we could do syntax-specific
merges (ignore comments/whitespace, for example).
i would surely have a use for it, as sometimes my internal team is not
_that_ good about trimming whitespace, and we have merges that succeed
except for their whitespace conflicts.
cheers,
martin
next prev parent reply other threads:[~2007-03-25 23:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-24 22:46 merge strategy request David Lang
2007-03-25 1:20 ` Johannes Schindelin
2007-03-25 1:18 ` David Lang
2007-03-25 4:31 ` Linus Torvalds
2007-03-25 6:25 ` David Lang
2007-03-25 7:17 ` Junio C Hamano
2007-03-25 23:34 ` Martin Langhoff [this message]
2007-03-25 23:16 ` David Lang
2007-03-25 23:44 ` Junio C Hamano
2007-03-26 0:11 ` Martin Langhoff
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=46a038f90703251634t2ab6a455t382ebe29cdb53667@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=david.lang@digitalinsight.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@linux-foundation.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).