From: Eyvind Bernhardsen <eyvind.bernhardsen@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Sixt <j.sixt@viscovery.net>,
Finn Arne Gangstad <finnag@pvv.org>,
"git@vger.kernel.org List" <git@vger.kernel.org>
Subject: [PATCH v4 0/3] CRLF merge conflict reduction, take 4
Date: Sun, 27 Jun 2010 21:43:04 +0200 [thread overview]
Message-ID: <cover.1277667177.git.eyvind.bernhardsen@gmail.com> (raw)
Only a few changes since the last round:
- added some paragraphs to the filter documentation in gitattributes to
explain why having normalizing filters is a good thing (comments
welcome)
- fixed the problem Johannes spotted in the eol=crlf optimization by
expanding CRLFs (ie not optimizing) if a smudge filter is configured
- moved the opening brace in my function definitions to the next line
Thanks for your input. I'm pretty happy with this now.
--
Eyvind
Eyvind Bernhardsen (3):
Avoid conflicts when merging branches with mixed normalization
Try normalizing files to avoid delete/modify conflicts when merging
Don't expand CRLFs when normalizing text during merge
Documentation/gitattributes.txt | 27 ++++++++++++++++++
cache.h | 1 +
convert.c | 37 +++++++++++++++++++++----
ll-merge.c | 13 +++++++++
merge-recursive.c | 44 ++++++++++++++++++++++++++++-
t/t6038-merge-text-auto.sh | 58 +++++++++++++++++++++++++++++++++++++++
6 files changed, 172 insertions(+), 8 deletions(-)
create mode 100755 t/t6038-merge-text-auto.sh
--
1.7.1.575.g383de
next reply other threads:[~2010-06-27 19:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-27 19:43 Eyvind Bernhardsen [this message]
2010-06-27 19:43 ` [PATCH v4 1/3] Avoid conflicts when merging branches with mixed normalization Eyvind Bernhardsen
2010-06-28 8:02 ` Finn Arne Gangstad
2010-06-28 19:32 ` [PATCH] Clarify text filter merge conflict reduction docs Eyvind Bernhardsen
2010-06-28 20:31 ` Finn Arne Gangstad
2010-06-29 16:19 ` Junio C Hamano
2010-06-29 21:18 ` Eyvind Bernhardsen
2010-06-30 17:46 ` Junio C Hamano
2010-06-30 21:32 ` Eyvind Bernhardsen
2010-07-01 3:33 ` Junio C Hamano
2010-06-30 8:20 ` Eyvind Bernhardsen
2010-06-30 15:15 ` Junio C Hamano
2010-06-27 19:43 ` [PATCH v4 2/3] Try normalizing files to avoid delete/modify conflicts when merging Eyvind Bernhardsen
2010-06-27 19:43 ` [PATCH v4 3/3] Don't expand CRLFs when normalizing text during merge Eyvind Bernhardsen
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=cover.1277667177.git.eyvind.bernhardsen@gmail.com \
--to=eyvind.bernhardsen@gmail.com \
--cc=finnag@pvv.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.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).