git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: problem when using --cc-cmd

From
Joe Perches <joe@perches.com>
Date
Apr 20, 2011, 03:03 UTC
Message-ID
<1303268630.24766.9.camel@Joe-Laptop>
In-Reply-To
<20110419215239.GA22632@elie>
On Tue, 2011-04-19 at 16:52 -0500, Jonathan Nieder wrote:
Show 8 quoted lines
> Thiago Farina wrote:
> > when I run:
> > $ git send-email --to linux-kernel@vger.kernel.org --cc-cmd
> > scripts/get_maintainer.pl foo
> > I'm getting some lines like:
> > Use of uninitialized value $cc in string eq at
> > /home/tfarina/libexec/git-core/git-send-email line 964.
> Yes, sounds like a bug.  Cc-ing some send-email people for tips.
I haven't seen this.

What versions of ./scripts/get_maintainer.pl and git are you using?

Show 13 quoted lines
> On the other hand, using --cc-cmd=scripts/get_maintainer.pl does not
> sound like a great idea to me.  On one hand the output of
> get_maintainer.pl is not an unadorned address per line like --cc-cmd
> expects.  On the other hand, at least some versions of
> get_maintainer.pl returned more addresses than are likely to be
> interested people (by using --git by default).
> 
> I think get_maintainer.pl is meant to be a starting point for tracking
> down who might be interested in a patch and should be followed by
> careful investigation.  (That means making sure that there is a
> reasonable number of people and the reasons given by --roles ouput
> make sense, and maybe even glancing at some messages by them from the
> relevant mailing list to make sure the script has not gone haywire.)
Jonathan is basically correct in the what he writes above.

I also think git history isn't a very good mechanism to rely on for determining MAINTAINERS, it should only be a fallback to determine who should receive a copy of a patch.

That said, I use scripts/get_maintainer.pl to generate to's and cc's. I do not use --git or --git-fallback and rely only on the MAINTAINERS file pattern matching.

Here are the settings I use:
$ cat ~/.gitconfig
[sendemail]
	chainreplyto = false
	thread = false
	suppresscc = self
	tocmd = ~/bin/to.sh
	cccmd = ~/bin/cc.sh

$ 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
Previous: Jonathan NiederNext: Thiago Farina
Message 3 of 10 in “problem when using --cc-cmd”
  1. Thiago FarinaApr 17, 2011
  2. Jonathan NiederApr 19, 2011
  3. Joe PerchesApr 20, 2011
  4. Thiago FarinaApr 20, 2011
  5. Joe PerchesApr 20, 2011
  6. git-send-email: Validate recipient_cmd (to-cmd, cc-cmd) addressesJoe Perches, Apr 20, 2011
  7. Ævar Arnfjörð BjarmasonApr 20, 2011
  8. Joe PerchesApr 20, 2011
  9. Ævar Arnfjörð BjarmasonApr 20, 2011
  10. Joe PerchesApr 20, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.