From: Jeff King <peff@peff.net>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Arafangion <thestar@fussycoder.id.au>, git@vger.kernel.org
Subject: Re: [PATCH] git-send-email: provide hook to send lines more than 998 symbols
Date: Fri, 21 Nov 2008 07:04:35 -0500 [thread overview]
Message-ID: <20081121120435.GC3747@sigill.intra.peff.net> (raw)
In-Reply-To: <5ec8ebd50811210237kd6f9341q23bc69b6ffcc2a87@mail.gmail.com>
On Fri, Nov 21, 2008 at 12:37:08PM +0200, Andy Shevchenko wrote:
> > As a curiosity, why is such a check even neccessary?
> I'm not an author of that strange check (possible it's somehow related
> to b8ebe08b9a643f432866eb7150c3b20d59b755f2)
I am the author, and it was a direct response to a user who had
something in his mail path munging overly long lines (which are, in
fact, disallowed by rfc 2822).
Read this thread:
http://thread.gmane.org/gmane.comp.version-control.git/70847
which contains the problem report and the patches. We could take this
one step further (but didn't at the time) by QP-encoding the body part
with long lines, which is what a normal MUA would do. Since the
receiving tools for git handle this situation, it should work fine. I
think such a patch would be welcome.
-Peff
next prev parent reply other threads:[~2008-11-21 12:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 9:59 [PATCH] git-send-email: provide hook to send lines more than 998 symbols Andy Shevchenko
2008-11-21 10:34 ` Arafangion
2008-11-21 10:37 ` Andy Shevchenko
2008-11-21 10:52 ` Teemu Likonen
2008-11-21 10:55 ` Andy Shevchenko
2008-11-21 11:09 ` Arafangion
2008-11-21 11:46 ` Andreas Ericsson
2008-11-21 12:04 ` Jeff King [this message]
2008-11-21 11:58 ` Jeff King
2008-11-21 12:49 ` Michael J Gruber
2008-11-21 13:29 ` Andy Shevchenko
2008-11-21 14:08 ` Jeff King
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=20081121120435.GC3747@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=andy.shevchenko@gmail.com \
--cc=git@vger.kernel.org \
--cc=thestar@fussycoder.id.au \
/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).