> -----Original Message-----
> From: Stefan Beller
> Sent: Monday, October 10, 2016 14:43
>
> +cc Xiaolong Ye <xiaolong.ye@xxxxxxxxx>
>
> On Sun, Oct 9, 2016 at 2:26 PM, Jason Pyeron <jpyeron@xxxxxxxx> wrote:
> >> -----Original Message-----
> >> From: Ian Kelling
> >> Sent: Sunday, October 09, 2016 15:03
> >>
> >> I've got patches in various projects, and I don't have
> time to keep up
> >> with the mailing list, but I'd like to help out with
> >> maintenance of that
> >> code, or the functions/files it touches. People don't cc me.
> >> I figure I
> >> could filter the list, test patches submitted, commits made,
> >> mentions of
> >> files/functions, build filters based on the code I have in
> >> the repo even
> >> if it's been moved or changed subsequently. I'm wondering
> what other
> >> people have implemented already for automation around
> this, or general
> >> thoughts. Web search is not showing me much.
> >>
> >
> > One thought would be to apply every patch automatically (to
> the branches of interest?). Then trigger on the [successful] changed
> > code. This would simplify the logic to working on the
> source only and not parsing the emails.
> >
> > -Jason
> >
>
> I think this is currently attempted by some kernel people.
> However it is very hard to tell where to apply a patch, as it
This is one of the reasons why I use bundles instead of format patch.
> is not formalized.
> See the series that was merged at 72ce3ff7b51c
> ('xy/format-patch-base'),
> which adds a footer to the patch, that tells you where
> exactly a patch ought
> to be applied.
Cant wait for that.
>
> The intention behind that series was to have some CI system hooked up
> and report failures to the mailing list as well IIUC. Maybe
> that helps with
> your use case, too?
I envisioned that it would try for each head he was interested in.