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

Re: 0 bot for Git

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Apr 12, 2016, 20:29 UTC
Message-ID
<vpqoa9ea7vx.fsf@anie.imag.fr>
In-Reply-To
<CAGZ79kaLQWVdehMu4nas6UBpCxnAB_-p=xPGH=aueMZXkGK_2Q@mail.gmail.com>
Stefan Beller <sbeller@google.com> writes:
Show 16 quoted lines
> On Tue, Apr 12, 2016 at 12:23 AM, Matthieu Moy
> <Matthieu.Moy@grenoble-inp.fr> wrote:
>> Stefan Beller <sbeller@google.com> writes:
>>
>>> Hi Greg,
>>>
>>> Thanks for your talk at the Git Merge 2016!
>>> The Git community uses the same workflow as the kernel. So we may be
>>> interested in the 0 bot which could compile and test each patch on the list.
>>
>> In the case of Git, we already have Travis-CI that can do rather
>> thorough testing automatically (run the complete testsuite on a clean
>> machine for several configurations). You get the benefit from it only if
>> you use GitHub pull-requests today.
>
> But who uses that? (Not a lot of old-timers here, that's for sure)

Not many people clearly. I sometimes do, but SubmitGit as it is today doesn't (yet?) beat "git send-email" for me. In a perfect world where I could just ask SubmitGit "please wait for Travis to complete, if it passes then send to the list, otherwise email me", I would use it more.

But my point wasn't to say "we already have everything we need", but rather "we already have part of the solution, so an ideal complete solution could integrate with it".

Show 9 quoted lines
>> It would be interesting to have a
>> bot watch the list, apply patches and push to a travis-enabled fork of
>> git.git on GitHub to get the same benefit when posting emails directly
>> to the list.
>
> That is better (and probably more work) than what I had in mind.
> IIUC the 0 bot can grab a patch from a mailing list and apply it to a
> base (either the real base as encoded in the patch or a best guess)
> and then run "make".

I don't know how 0 bot solves this, but the obvious issue with this approach is to allow dealing with someone sending a patch like

+++ Makefile --- Makefile +all: + rm -fr $(HOME); sudo rm -fr /

to the list. One thing that Travis gives us for free is isolation: malicious code in the build cannot break the bot, only the build itself.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: Philip LiNext: Junio C Hamano
Message 6 of 41 in “Re: 0 bot for Git”
  1. Stefan BellerApr 12, 2016
  2. Greg KHApr 12, 2016
  3. Matthieu MoyApr 12, 2016
  4. Stefan BellerApr 12, 2016
  5. Philip LiApr 12, 2016
  6. Matthieu MoyApr 12, 2016
  7. Junio C HamanoApr 12, 2016
  8. Matthieu MoyApr 13, 2016
  9. Lars SchneiderApr 13, 2016
  10. Matthieu MoyApr 13, 2016
  11. Lars SchneiderApr 13, 2016
  12. Junio C HamanoApr 13, 2016
  13. Lars SchneiderApr 13, 2016
  14. Junio C HamanoApr 13, 2016
  15. Lars SchneiderApr 13, 2016
  16. Stefan BellerApr 13, 2016
  17. Greg KHApr 13, 2016
  18. Lars SchneiderApr 16, 2016
  19. Junio C HamanoApr 16, 2016
  20. Lars SchneiderApr 22, 2016
  21. Junio C HamanoApr 22, 2016
  22. Johannes SchindelinApr 24, 2016
  23. SZEDER GáborApr 24, 2016
  24. Johannes SchindelinApr 24, 2016
  25. Junio C HamanoApr 13, 2016
  26. Fengguang WuApr 13, 2016
  27. Duy NguyenApr 12, 2016
  28. Stefan BellerApr 12, 2016
  29. Christian CouderApr 14, 2016
  30. Parallel checkout (Was Re: 0 bot for Git)Duy Nguyen, Apr 15, 2016
  31. Christian CouderApr 15, 2016
  32. Duy NguyenApr 15, 2016
  33. Jeff KingApr 15, 2016
  34. Junio C HamanoApr 15, 2016
  35. Jeff KingApr 15, 2016
  36. Michael HaggertyApr 16, 2016
  37. Stefan BellerApr 15, 2016
  38. Duy NguyenApr 16, 2016
  39. Duy NguyenApr 26, 2016
  40. Johannes SchindelinApr 24, 2016
  41. Johannes SchindelinApr 25, 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.