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

Re: [Announce] submitGit for patch submission (was "Diffing submodule does not yield complete logs")

From
Junio C Hamano <gitster@pobox.com>
Date
May 22, 2015, 14:17 UTC
Message-ID
<xmqq8ucghf2s.fsf@gitster.dls.corp.google.com>
In-Reply-To
<CAFY1edY3+Wt-p2iQ5k64Fg-nMk2PmRSvhVkQSVNw94R18uPV2Q@mail.gmail.com>
Roberto Tyley <roberto.tyley@gmail.com> writes:
> Hello, I'm stepping up to do that work :) Or at least, I'm implementing a
> one-way GitHub PR -> Mailing list tool, called submitGit:
>
> https://submitgit.herokuapp.com/
Yay ;-)
Show 5 quoted lines
> Here's what a user does:
>
> * create a PR on https://github.com/git/git
> * logs into https://submitgit.herokuapp.com/ with GitHub auth
> * selects their PR on https://submitgit.herokuapp.com/git/git/pulls
Reasonable.
> * gets submitGit to email the PR as patches to themselves, in order to
> check it looks ok

I can see you are trying to be careful by doing this, but I am not sure if this step would actually help. Those who are not familiar with Git development are not expected to know what is "ok" in their original commit, and if they find bad formatting done by submitGit (e.g. adds their PR message before the three-dash line instead of after it), they cannot do much about it anyway.

> * when they're ready, get submitGit to send it to the mailing list on
> their behalf
Nice.
> All discussion of the patch *stays* on the mailing list

Can you identify a reroll of an earlier submission? If you can use the in-reply-to and make it a follow-up to the previous round, that would be great.

Previous: Stefan NäweNext: Philip Oakley
Message 10 of 21 in “[Announce] submitGit for patch submission (was "Diffing submodule does not yield complete logs")”
  1. Roberto TyleyMay 22, 2015
  2. Johannes SchindelinMay 22, 2015
  3. Johannes SchindelinMay 22, 2015
  4. Philip OakleyMay 22, 2015
  5. Johannes SchindelinMay 22, 2015
  6. Philip OakleyMay 22, 2015
  7. Johannes SchindelinMay 23, 2015
  8. Sebastian SchuberthMay 22, 2015
  9. Stefan NäweMay 22, 2015
  10. Junio C HamanoMay 22, 2015
  11. Philip OakleyMay 22, 2015
  12. Stefan BellerMay 22, 2015
  13. Johannes SchindelinMay 22, 2015
  14. Junio C HamanoMay 22, 2015
  15. Stefan BellerMay 22, 2015
  16. Johannes SchindelinMay 23, 2015
  17. Matthieu MoyMay 23, 2015
  18. Matthieu MoyMay 22, 2015
  19. Junio C HamanoMay 22, 2015
  20. Stefan BellerMay 22, 2015
  21. Johannes SchindelinMay 23, 2015

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.