From: Michael J Gruber <git@drmicha.warpmail.net>
To: Jeff King <peff@peff.net>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] git-send-email: provide hook to send lines more than 998 symbols
Date: Fri, 21 Nov 2008 13:49:18 +0100 [thread overview]
Message-ID: <4926AE4E.5000604@drmicha.warpmail.net> (raw)
In-Reply-To: <20081121115813.GB3747@sigill.intra.peff.net>
Jeff King venit, vidit, dixit 21.11.2008 12:58:
> On Fri, Nov 21, 2008 at 11:59:24AM +0200, Andy Shevchenko wrote:
>
>> By default git-send-email does not accept patch which is contain lines longer
>> than 998 symbols. Sometime it's inconvenient, i.e. you have a long list in one
>> variable in shell script. So, define environment variable
>> GIT_SEND_EMAIL_LONGLINE to something to avoid that restriction.
>
> This already exists as "git send-email --no-validate", which
> unfortunately doesn't seem to be documented. Care to send in a
> documentation patch instead?
In fact it is documented in git-send-email.txt:
--[no-]validate::
Perform sanity checks on patches.
Currently, validation means the following:
+
--
* Warn of patches that contain lines longer than
998 characters; this
is due to SMTP limits as described by
http://www.ietf.org/rfc/rfc2821.txt.
--
+
Default is the value of 'sendemail.validate'; if this is not set,
default to '--validate'.
Cheers,
Michael
next prev parent reply other threads:[~2008-11-21 12:50 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
2008-11-21 11:58 ` Jeff King
2008-11-21 12:49 ` Michael J Gruber [this message]
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=4926AE4E.5000604@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=andy.shevchenko@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).