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

Re: RFE: use patchwork to submit a patch

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Oct 10, 2019, 20:20 UTC
Message-ID
<20191010202049.GB191800@google.com>
In-Reply-To
<20191010144150.hqiosvwolm3lmzp5@chatter.i7.local>

(+cc: git) Hi,

Konstantin Ryabitsev wrote[1]:
Show 5 quoted lines
> How I envision this would work:
>
> - user creates an account (which requires a mail confirmation)
> - they choose a "submit patch" option from the menu
> - the patch submission screen has a succession of screens:

Interesting! This reminds me a bit of https://gitgitgadget.github.io (except using patchwork instead of github pull requests as substrate).

That leads me to wonder: should these kinds of tools share some code? Are there any subtleties that web-to-mail patch submission interfaces have in common or can learn from each other?

Thanks, Jonathan

[1] https://lore.kernel.org/workflows/20191010144150.hqiosvwolm3lmzp5@chatter.i7.local/
Next: Jonathan Nieder
Message 1 of 3 in “Re: RFE: use patchwork to submit a patch”
  1. Jonathan NiederOct 10, 2019
  2. Jonathan NiederOct 10, 2019
  3. Eric WongOct 10, 2019

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.