patch, 19 partsCC in git cover letter vs patches (was Re: [PATCH 0/19] get rid of superfluous __GFP_REPORT)

Trimming CC list + CC git folks

Hi Michal,

On Monday 11 April 2016 04:37 PM, Michal Hocko wrote:

I have a git question if you didn't mind w.r.t. this series. Maybe there's an obvious answer... I'm using git 2.5.0

I was wondering how you manage to union the individual patch CC in just the cover letter w/o bombarding everyone with everything.

Thx, -Vineet

-- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

On Wed 13-04-16 16:51:37, Vineet Gupta wrote:

I am using the following flow:

$ rm *.patch $ for format-patch range $ git send-email [--to resp. --cc for all patches] --cc-cmd ./cc-cmd-only-cover.sh --compose *.patch

$ cat ./cc-cmd-only-cover.sh #!/bin/bash

# --compose with generate *gitsendemail.msg file
# --cover-letter expects *cover-letter* file
if [[ $1 == *gitsendemail.msg* || $1 == *cover-letter* ]]; then
        grep '<.*@.*>' -h *.patch | sed 's/^.*: //' | sort | uniq
fi

it is a little bit coarse and it would be great if git had a default option for that but this seems to be working just fine for patch-bombs where the recipients only have to care about their parts and the cover for the overal idea of the change.

HTH