All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 1/2] patman: add option for limiting the Cc list
Date: Fri, 8 Jun 2018 13:59:24 -0800	[thread overview]
Message-ID: <CAPnjgZ0TzPP7x1MVnRe3pV3x323NPR5yv-z0SytZUBC3zA0tBw@mail.gmail.com> (raw)
In-Reply-To: <20180607084507.9382-1-judge.packham@gmail.com>

On 7 June 2018 at 00:45, Chris Packham <judge.packham@gmail.com> wrote:
> Many mailing-lists consider a long Cc list a sign of spam and will
> either drop the message or mark it for moderation. Because patman
> automatically invokes get_maintainer.pl the Cc list can expand
> unexpectedly. Allow the user to specify a limit for the Cc list.
>
> This limit is applied after removing any known bouncing addresses. By
> default no limit is applied.
>
> Signed-off-by: Chris Packham <judge.packham@gmail.com>
> ---
> I've fallen foul of the u-boot ML Cc limit a few times recently. I'm not
> sure what the actual limit is so I've left patman's default behaviour
> unlimited.
>
> Changes in v3:
> - update func_test
>
> Changes in v2:
> - make default None to allow limit 0 to suppress the list completely
>
>  tools/patman/func_test.py | 3 ++-
>  tools/patman/patman.py    | 4 +++-
>  tools/patman/series.py    | 5 ++++-
>  3 files changed, 9 insertions(+), 3 deletions(-)

Reviewed-by: Simon Glass <sjg@chromium.org>

  parent reply	other threads:[~2018-06-08 21:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-07  8:45 [U-Boot] [PATCH v3 1/2] patman: add option for limiting the Cc list Chris Packham
2018-06-07  8:45 ` [U-Boot] [PATCH v3 2/2] patman: add test for SPDX license Chris Packham
2018-06-08 21:59   ` Simon Glass
2018-06-23 14:06     ` Simon Glass
2018-06-08 21:59 ` Simon Glass [this message]
2018-06-23 14:06   ` [U-Boot] [PATCH v3 1/2] patman: add option for limiting the Cc list Simon Glass

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=CAPnjgZ0TzPP7x1MVnRe3pV3x323NPR5yv-z0SytZUBC3zA0tBw@mail.gmail.com \
    --to=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.