git/list[1] front-page[2] threads[3] people[4] search[5] about
 

RE: How to watch a mailing list & repo for patches which affect a certain area of code?

From
Jason Pyeron <jpyeron@pdinc.us>
Date
Oct 9, 2016, 21:26 UTC
Message-ID
<4B3747D8D2724E98B6AC000FE4072A09@black7>
In-Reply-To
<1476039798.3060702.750483225.1DE6C48B@webmail.messagingengine.com>
Show 17 quoted lines
> -----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
Previous: Ian KellingNext: Stefan Beller
Message 2 of 9 in “How to watch a mailing list & repo for patches which affect a certain area of code?”
  1. Ian KellingOct 9, 2016
  2. Jason PyeronOct 9, 2016
  3. Stefan BellerOct 10, 2016
  4. Jason PyeronOct 10, 2016
  5. Stefan BellerOct 10, 2016
  6. Jason PyeronOct 10, 2016
  7. Ian KellingOct 10, 2016
  8. Eric WongOct 10, 2016
  9. Jakub NarębskiOct 10, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.