From: Larsen <larsen007@web.de>
To: development@lists.ipfire.org
Subject: Re: Problem with whitespace in patches
Date: Fri, 05 Jun 2015 15:29:31 +0200 [thread overview]
Message-ID: <op.xzrefhzwcahio0@atl-uetersen.atlantisgmbh.local> (raw)
In-Reply-To: <1433510732.27049.11.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 771 bytes --]
On Fri, 05 Jun 2015 15:25:32 +0200, Michael Tremer
<michael.tremer(a)ipfire.org> wrote:
>> Then, I switched views to have the header displayed, too, and saved it
>> as a file.
>> Compared to the file created by TortoiseGit and now I can solve this
>> riddle:
>> There we have superfluous whitespace in front of every line without a +
>> or -
>> (as you noticed before).
>
> I cannot really understand why this would make the email better readable
> or anything.
I know, it´s absolutely stupid. The dev must have had a bad day or
something...
> Let us know about your experience with Thunderbird.
http://patchwork.ipfire.org/patch/15/ was sent with TB.
Ignoring the aforementioned points that patch is still missing, would it
theoretically merge?
Lars
prev parent reply other threads:[~2015-06-05 13:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1433079323.3370.92.camel@ipfire.org>
2015-06-01 20:59 ` [PATCH] Fix hardcoded strings in pppsetup.cgi Larsen
2015-06-01 21:57 ` Aw: " Bernhard Bitsch
2015-06-02 6:58 ` Larsen
2015-06-02 8:51 ` Aw: " Bernhard Bitsch
2015-06-02 10:04 ` Larsen
2015-06-02 19:49 ` Larsen
2015-06-02 20:01 ` Michael Tremer
2015-06-02 21:05 ` Larsen
2015-06-02 21:07 ` Larsen
2015-06-04 16:23 ` Michael Tremer
2015-06-04 20:52 ` Problem with whitespace in patches Larsen
2015-06-05 13:25 ` Michael Tremer
2015-06-05 13:29 ` Larsen [this message]
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=op.xzrefhzwcahio0@atl-uetersen.atlantisgmbh.local \
--to=larsen007@web.de \
--cc=development@lists.ipfire.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