From: Aaron Schrab <aaron@schrab.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, sunshine@sunshineco.com,
bturner@atlassian.com, Marc Strapetz <marc.strapetz@syntevo.com>
Subject: Re: [PATCH v3] Documentation: declare "core.ignorecase" as internal variable
Date: Wed, 27 Jun 2018 19:09:57 -0400 [thread overview]
Message-ID: <20180627230957.GB15174@pug.qqx.org> (raw)
In-Reply-To: <xmqqzhzgdoyb.fsf@gitster-ct.c.googlers.com>
At 12:11 -0700 27 Jun 2018, Junio C Hamano <gitster@pobox.com> wrote:
>Hmph. Do other people have difficulty applying this patch to their
>trees? It is just several lines long so I could retype it myself,
>but I guess "Content-Type: text/plain; charset=utf-8; format=flowed"
>has destroyed formatting of the patch rather badly.
Yes, format=flowed requires lines that start with a space (along with
'>' or 'From ') to be space-stuffed, adding a leading space. This will
affect context lines in patches.
I was able to apply it cleanly (I think) by sending the message to:
sed '/@@/,$s/^ / /' | git am
That's replacing two leading spaces with one.
next prev parent reply other threads:[~2018-06-27 23:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-24 10:05 [PATCH] Documentation: declare "core.ignorecase" as internal variable Marc Strapetz
2018-06-24 10:19 ` Eric Sunshine
2018-06-24 10:44 ` [PATCH v2] " Marc Strapetz
2018-06-24 11:26 ` Sascha Silbe
2018-06-24 13:47 ` Torsten Bögershausen
2018-06-26 21:50 ` [PATCH v3] " Marc Strapetz
2018-06-27 19:11 ` Junio C Hamano
2018-06-27 23:09 ` Aaron Schrab [this message]
2018-06-28 11:36 ` Marc Strapetz
2018-06-28 11:21 ` [PATCH v4] Documentation: declare "core.ignoreCase" " Marc Strapetz
2018-06-28 16:47 ` Junio C Hamano
2018-06-28 16:58 ` Torsten Bögershausen
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=20180627230957.GB15174@pug.qqx.org \
--to=aaron@schrab.com \
--cc=bturner@atlassian.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=marc.strapetz@syntevo.com \
--cc=sunshine@sunshineco.com \
/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).