[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PULL 00/33] Trivial branch patches

From: Laurent Vivier
Subject: Re: [PULL 00/33] Trivial branch patches
Date: Tue, 10 Mar 2020 13:34:29 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1

Le 10/03/2020 à 13:13, Kevin Wolf a écrit :
> Am 10.03.2020 um 13:00 hat Philippe Mathieu-Daudé geschrieben:
>> On 3/10/20 12:45 PM, Kevin Wolf wrote:
>>> Am 10.03.2020 um 09:02 hat Laurent Vivier geschrieben:
>>>> Le 09/03/2020 à 20:30, Philippe Mathieu-Daudé a écrit :
>>>>> On 3/9/20 8:17 PM, Michael S. Tsirkin wrote:
>>>>>> On Mon, Mar 09, 2020 at 04:08:04PM +0100, Laurent Vivier wrote:
>>>>>>> The following changes since commit
>>>>>>> 7a5853cec479a448edae0fb2aaf4e2f78c9c774d:
>>>>>>>     Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into
>>>>>>> staging (2020-03-09 10:32:53 +0000)
>>>>>>> are available in the Git repository at:
>>>>>>>     git://github.com/vivier/qemu.git tags/trivial-branch-pull-request
>>>>>>> for you to fetch changes up to 916c92503bd5348a33e561db600d8894bde636bb:
>>>>>>>     monitor/hmp-cmds: Remove redundant statement in
>>>>>>> hmp_rocker_of_dpa_groups() (2020-03-09 15:59:31 +0100)
>>>>>> Could you avoid CC everyone involved on the whole PULL req?
>>>>>> I was involved in a patch or two and don't really need to see
>>>>>> the whole series. Just the cover and the relevant patches
>>>>>> would be enough - if I do want it there's always lore.
>>>>> I suppose Laurent used git-publish, which has this limitation.
>>>> Yes, I use git publish and CC are automatically added.
>>>> Philippe, you told me some time ago you have a patch to fix this
>>>> behaviour and only CC people on a patch base. Is it available?
>> I guess you mean https://github.com/philmd/git-publish/commit/5bab6e2cc77, I
>> haven't improved it but plan to spend time on it during my next holidays.
>>> Actually, I don't think it's even necessary to CC anyone at all (except
>>> the relevant lists) for pull requests. These patches were already
>>> reviewed.
>> Well as a contributor I find useful to get notified when patches are merged.
> Hm, I guess a matter of different preferences then.
>> I guess remember some time ago patchew (or another bot?) was sending a
>> notification on pull request merged, this was even more useful than Cc'ing
>> ppl on pull-req. It is also helpful when you track someone else patch on the
>> list.
>> Since most of the maintainers now include the patch RFC822 Message-Id, it is
>> now easy for a bot to reply to patch taken from the last.
> I don't remember anything like this, but having an automatic reply to
> the email thread of each merged patch series might be a good idea.

I receive an email for each merge [1]

There is a mailing list for that:



[1] https://lists.nongnu.org/archive/html/qemu-commits/2020-03/index.html

reply via email to

[Prev in Thread] Current Thread [Next in Thread]