From: "Jason Pyeron" <jpyeron@pdinc.us>
To: <git@vger.kernel.org>
Cc: "'Ian Kelling'" <ian@iankelling.org>,
"'Stefan Beller'" <sbeller@google.com>,
"'Xiaolong Ye'" <xiaolong.ye@intel.com>
Subject: RE: How to watch a mailing list & repo for patches which affect a certain area of code?
Date: Mon, 10 Oct 2016 14:56:34 -0400 [thread overview]
Message-ID: <AB0A757A7BE241B39C8193A633C61FED@black7> (raw)
In-Reply-To: <CAGZ79kaHOBaVCsVPen-K_5LyitcDzVbjL_kAqMkYKk_fQxH4PQ@mail.gmail.com>
> -----Original Message-----
> From: Stefan Beller
> Sent: Monday, October 10, 2016 14:43
>
> +cc Xiaolong Ye <xiaolong.ye@intel.com>
>
> On Sun, Oct 9, 2016 at 2:26 PM, Jason Pyeron <jpyeron@pdinc.us> 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.
next prev parent reply other threads:[~2016-10-10 18:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 19:03 How to watch a mailing list & repo for patches which affect a certain area of code? Ian Kelling
2016-10-09 21:26 ` Jason Pyeron
2016-10-10 18:42 ` Stefan Beller
2016-10-10 18:56 ` Jason Pyeron [this message]
2016-10-10 19:08 ` Stefan Beller
2016-10-10 19:40 ` How to watch a mailing list & repo for patches which affect a certain area of code? [OT] Jason Pyeron
2016-10-10 20:49 ` How to watch a mailing list & repo for patches which affect a certain area of code? Ian Kelling
2016-10-10 15:11 ` Eric Wong
2016-10-10 18:10 ` Jakub Narębski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AB0A757A7BE241B39C8193A633C61FED@black7 \
--to=jpyeron@pdinc.us \
--cc=git@vger.kernel.org \
--cc=ian@iankelling.org \
--cc=sbeller@google.com \
--cc=xiaolong.ye@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).