From: "Jason Pyeron" <jpyeron@pdinc.us>
To: <git@vger.kernel.org>
Cc: "'Ian Kelling'" <ian@iankelling.org>
Subject: RE: How to watch a mailing list & repo for patches which affect a certain area of code?
Date: Sun, 9 Oct 2016 17:26:16 -0400 [thread overview]
Message-ID: <4B3747D8D2724E98B6AC000FE4072A09@black7> (raw)
In-Reply-To: <1476039798.3060702.750483225.1DE6C48B@webmail.messagingengine.com>
> -----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
next prev parent reply other threads:[~2016-10-09 21:26 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 [this message]
2016-10-10 18:42 ` Stefan Beller
2016-10-10 18:56 ` Jason Pyeron
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=4B3747D8D2724E98B6AC000FE4072A09@black7 \
--to=jpyeron@pdinc.us \
--cc=git@vger.kernel.org \
--cc=ian@iankelling.org \
/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).