{"thread":{"id":"42015","subject":"CC in git cover letter vs patches (was Re: [PATCH 0/19] get rid of superfluous __GFP_REPORT)","startedAt":"2016-04-13T11:21:37Z","lastAt":"2016-04-13T13:33:47Z","messageCount":2,"participants":["Vineet Gupta","Michal Hocko"],"isPatch":true,"patchVersion":1,"patchTotal":19},"messages":[{"id":"283312","messageId":"570E2BC1.8050809@synopsys.com","threadId":"42015","inReplyTo":"1460372892-8157-1-git-send-email-mhocko@kernel.org","subject":"CC in git cover letter vs patches (was Re: [PATCH 0/19] get rid of superfluous __GFP_REPORT)","fromName":"Vineet Gupta","fromEmail":"vineet.gupta1@synopsys.com","sentAt":"2016-04-13T11:21:37Z","receivedAt":"2016-04-13T11:21:37Z","isPatch":true,"sender":{"key":"vineet.gupta1@synopsys.com","avatar":null},"body":"Trimming CC list + CC git folks\n\nHi Michal,\n\nOn Monday 11 April 2016 04:37 PM, Michal Hocko wrote:\n> Hi,\n> this is the second version of the patchset previously sent [1]\n\nI have a git question if you didn't mind w.r.t. this series. Maybe there's an\nobvious answer... I'm using git 2.5.0\n\nI was wondering how you manage to union the individual patch CC in just the cover\nletter w/o bombarding everyone with everything.\n\nThx,\n-Vineet\n\n--\nTo unsubscribe, send a message with 'unsubscribe linux-mm' in\nthe body to majordomo@kvack.org.  For more info on Linux MM,\nsee: http://www.linux-mm.org/ .\nDon't email: <a href=mailto:\"dont@kvack.org\"> email@kvack.org </a>\n"},{"id":"283373","messageId":"20160413133347.GJ14351@dhcp22.suse.cz","threadId":"42015","inReplyTo":"570E2BC1.8050809@synopsys.com","subject":"Re: CC in git cover letter vs patches (was Re: [PATCH 0/19] get rid of superfluous __GFP_REPORT)","fromName":"Michal Hocko","fromEmail":"mhocko@kernel.org","sentAt":"2016-04-13T13:33:47Z","receivedAt":"2016-04-13T13:33:47Z","isPatch":true,"sender":{"key":"mhocko@kernel.org","avatar":null},"body":"On Wed 13-04-16 16:51:37, Vineet Gupta wrote:\n> Trimming CC list + CC git folks\n> \n> Hi Michal,\n> \n> On Monday 11 April 2016 04:37 PM, Michal Hocko wrote:\n> > Hi,\n> > this is the second version of the patchset previously sent [1]\n> \n> I have a git question if you didn't mind w.r.t. this series. Maybe there's an\n> obvious answer... I'm using git 2.5.0\n> \n> I was wondering how you manage to union the individual patch CC in just the cover\n> letter w/o bombarding everyone with everything.\n\nI am using the following flow:\n\n$ rm *.patch\n$ for format-patch range\n$ git send-email [--to resp. --cc for all patches] --cc-cmd ./cc-cmd-only-cover.sh --compose *.patch\n\n$ cat ./cc-cmd-only-cover.sh \n#!/bin/bash\n\n# --compose with generate *gitsendemail.msg file\n# --cover-letter expects *cover-letter* file\nif [[ $1 == *gitsendemail.msg* || $1 == *cover-letter* ]]; then\n        grep '<.*@.*>' -h *.patch | sed 's/^.*: //' | sort | uniq\nfi\n\nit is a little bit coarse and it would be great if git had a default\noption for that but this seems to be working just fine for patch-bombs\nwhere the recipients only have to care about their parts and the cover\nfor the overal idea of the change.\n\nHTH\n-- \nMichal Hocko\nSUSE Labs\n\n--\nTo unsubscribe, send a message with 'unsubscribe linux-mm' in\nthe body to majordomo@kvack.org.  For more info on Linux MM,\nsee: http://www.linux-mm.org/ .\nDon't email: <a href=mailto:\"dont@kvack.org\"> email@kvack.org </a>\n"}]}