From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: rebasing, git-am and whitespace cleanup conundrims
Date: Thu, 26 Oct 2006 11:49:36 +1300 [thread overview]
Message-ID: <46a038f90610251549u46af5ab9gefb56423fb663e96@mail.gmail.com> (raw)
Hola!
i'm going through a rebase of a long series of patches (~50) that have
quite a bit of trailing whitespace. Once the rebase is done on my repo
(resolving all the code level conflicts), I want to re-rebase it on
top of the same commit but cleaning up trailing whitespace.
The problem is that upstream has 'some' trailing whitespace. The
policy is to reject "new" trailing whitespace and cleanup in stages to
avoid big merge conflicts and stuff.
Now, once the early patches are "in" with --whitespace=trim, the
following patches don't apply anymore :-/ and I can't just trim
whitespace in the whole patch series automatically.
Is there any way to get git-apply to ignore whitespace differences
when applying like GNU patch -l?
When -3 is passed, it must be calling the merge utility from
merge_file() -- which doesn't do 'ignore-whitespace'. But if it's a
straight patch application, it should be possible to do something like
that... maybe?
cheers,
reply other threads:[~2006-10-25 22:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46a038f90610251549u46af5ab9gefb56423fb663e96@mail.gmail.com \
--to=martin.langhoff@gmail.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).