From: Larsen <larsen007@web.de>
To: development@lists.ipfire.org
Subject: Re: Removed code by mistake?
Date: Tue, 02 Jun 2015 21:17:24 +0200 [thread overview]
Message-ID: <op.xzmajad1cahio0@honk.fritz.box> (raw)
In-Reply-To: <1433272018.3370.259.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 471 bytes --]
On Tue, 02 Jun 2015 21:06:58 +0200, Michael Tremer <michael.tremer(a)ipfire.org> wrote:
> This email you just sent does not use line-wrapping as you can see by
> the longish sentence above, but it would be fine if it would use that
> for written text because that is better readable when it wraps around
> after 80 characters or so.
I don´t think there is a setting to only disable line-wrapping
for inline patches ;-)
Will wrap manually then.
Lars
prev parent reply other threads:[~2015-06-02 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 15:11 Larsen
2015-06-02 17:36 ` Michael Tremer
2015-06-02 19:03 ` Larsen
2015-06-02 19:06 ` Michael Tremer
2015-06-02 19:17 ` 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.xzmajad1cahio0@honk.fritz.box \
--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