From: "Richard Hartmann" <richih.mailinglist@gmail.com>
To: "Samuel Tardieu" <sam@rfc1149.net>
Cc: git@vger.kernel.org, markus.heidelberg@web.de
Subject: Re: Conflict-free merging (i.e. concat) of conflicting branches?
Date: Sun, 16 Nov 2008 22:43:44 +0100 [thread overview]
Message-ID: <2d460de70811161343w52a9a4deo7c8d9bb155514de0@mail.gmail.com> (raw)
In-Reply-To: <2008-11-16-15-19-47+trackit+sam@rfc1149.net>
On Sun, Nov 16, 2008 at 15:19, Samuel Tardieu <sam@rfc1149.net> wrote:
> You can use a custom merge driver especially designed for this case.
> See gitattributes(5) man page for an explanation of how it works.
Thanks.
Richard
next prev parent reply other threads:[~2008-11-16 21:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 13:50 Conflict-free merging (i.e. concat) of conflicting branches? Richard Hartmann
2008-11-16 14:19 ` Samuel Tardieu
2008-11-16 21:43 ` Richard Hartmann [this message]
2008-11-16 16:28 ` Junio C Hamano
2008-11-16 21:44 ` Richard Hartmann
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=2d460de70811161343w52a9a4deo7c8d9bb155514de0@mail.gmail.com \
--to=richih.mailinglist@gmail.com \
--cc=git@vger.kernel.org \
--cc=markus.heidelberg@web.de \
--cc=sam@rfc1149.net \
/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).