From: Junio C Hamano <gitster@pobox•com>
To: "Kyle J. McKay" <mackyle@gmail•com>
Cc: git@vger•kernel.org, Michael Haggerty <mhagger@alum•mit.edu>
Subject: Re: [PATCH] hooks/post-receive-email: do not truncate messages at a '.' line
Date: Thu, 17 Jul 2014 12:36:13 -0700 [thread overview]
Message-ID: <xmqq38dzpykx.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <53b2ad7801889b49f04cb0ae7b0b37b@74d39fa044aa309eaea14b9f57fe79c> (Kyle J. McKay's message of "Thu, 17 Jul 2014 12:26:29 -0700")
"Kyle J. McKay" <mackyle@gmail•com> writes:
> There are two options to turn off this behavior, -i and -oi which
> are equivalent.
>
> The choice of which to use is based on the observation that -i
> appears to be the more commonly used option for this and that all
> current sendmail-compatible programs appear to accept both.
OK; I suspect some just accept but ignore, though.
> BTW, what is the status of post-receive-email?
I do not use either, but some people seem to consider multimail its
successor, so enhancements may have a wider audience there.
prev parent reply other threads:[~2014-07-17 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 19:26 [PATCH] hooks/post-receive-email: do not truncate messages at a '.' line Kyle J. McKay
2014-07-17 19:36 ` Junio C Hamano [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=xmqq38dzpykx.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=mackyle@gmail$(echo .)com \
--cc=mhagger@alum$(echo .)mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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