All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: "Rafał Miłecki" <zajec5@gmail.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: get_maintainer.pl and git send-email: 5.1.2 The recipient address <linux-mtd@lists.infradead.org)> is not a valid
Date: Wed, 14 Sep 2016 07:32:08 -0700	[thread overview]
Message-ID: <1473863528.32273.30.camel@perches.com> (raw)
In-Reply-To: <1473862411.32273.25.camel@perches.com>

On Wed, 2016-09-14 at 07:13 -0700, Joe Perches wrote:
> The scripts use --to-cmd to address the direct maintainers
> and cc-cmd to address indirect maintainers and mailing lists.

I neglected to mention I use a separate directory for each patch series
so there are no other files in the directory that could be scanned with
the wildcard use of '$(dirname $1)/*'

$ git format-patch -o <new_directory> ...

> $ cat ~/bin/to.sh
> #!/bin/bash
> 
> opts="--nogit --nogit-fallback --norolestats --pattern-depth=1"
> 
> if [[ $(basename $1) =~ ^0000- ]] ; then
>     ./scripts/get_maintainer.pl --nom $opts  $(dirname $1)/*
> else
>     maint=$(./scripts/get_maintainer.pl --nol $opts $1)
>     if [ "$maint" == "" ] ; then
> > 	echo "linux-kernel@vger.kernel.org"
>     else
> 	echo "$maint"
>     fi
> fi
> 
> $ cat ~/bin/cc.sh
> #!/bin/bash
> 
> opts="--nogit --nogit-fallback --norolestats"
> 
> if [[ $(basename $1) =~ ^0000- ]] ; then
>     ./scripts/get_maintainer.pl --nom $opts  $(dirname $1)/*
> else
>     ./scripts/get_maintainer.pl $opts $1
> fi
> 

      reply	other threads:[~2016-09-14 14:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14 10:45 get_maintainer.pl and git send-email: 5.1.2 The recipient address <linux-mtd@lists.infradead.org)> is not a valid Rafał Miłecki
2016-09-14 14:13 ` Joe Perches
2016-09-14 14:32   ` Joe Perches [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=1473863528.32273.30.camel@perches.com \
    --to=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zajec5@gmail.com \
    /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.