From: Justin Frankel <justin@cockos.com>
To: git@vger.kernel.org
Subject: [PATCH 0/2] git-merge: ignore space support
Date: Sat, 21 Aug 2010 22:43:21 -0700 [thread overview]
Message-ID: <20100822054321.GA64856@ns1.cockos.com> (raw)
Hello,
(Sorry if this is a duplicate, I'm thinking my MIME encoding was causing this
to get filtered).
I've added support for merging with ignoring line endings (specifically
--ignore-space-at-eol) when using recursive merging. I've added this as a
strategy-option, so that you can do:
git merge --strategy-option=ignore-space-at-eol <branch>
and
git rebase --strategy-option=ignore-space-at-eol <branch>
The only option I needed was ignore-space-at-eol, however it made some sense (to
me at least) to include the other xdiff options (ignore-space-change,
ignore-all-space, patient).
I researched why this wasn't supported already, and only found some vague
references to why it shouldn't be in there -- if so, I would like to hear that
explanation (it does seem to me like it should be a good thing to support, even
if you strongly discourage use of it -- it would have saved me many hours
yesterday had it been available, but that of course isn't git's fault, but
Xcode's. ).
Which branches should we derive from for things like this? The first patch is
for master, the second for next (there were enough changes in ll-merge that
the implementations are a bit different).
Thank you for your time, and I'm very happy to be using Git! It is wonderful.
Cheers,
Justin
next reply other threads:[~2010-08-22 5:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-22 5:43 Justin Frankel [this message]
2010-08-23 19:33 ` [PATCH 0/2] git-merge: ignore space support Jonathan Nieder
2010-08-23 20:34 ` Justin Frankel
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=20100822054321.GA64856@ns1.cockos.com \
--to=justin@cockos.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).