Re: [Announce] submitGit for patch submission (was "Diffing submodule does not yield complete logs")
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- May 22, 2015, 09:42 UTC
- Message-ID
- <73db761f3c737965f64ac45005f7a716@www.dscho.org>
- In-Reply-To
- <CAFY1edY3+Wt-p2iQ5k64Fg-nMk2PmRSvhVkQSVNw94R18uPV2Q@mail.gmail.com>
Hi Roberto,
On 2015-05-22 10:33, Roberto Tyley wrote:
Show 22 quoted lines
> On Tuesday, 19 May 2015, Stefan Beller <sbeller@google.com> wrote: >> On Tue, May 19, 2015 at 12:29 PM, Robert Dailey >> <rcdailey.lists@gmail.com> wrote: >> > How do you send your patches inline? > [snip] >> This workflow discussion was a topic at the GitMerge2015 conference, >> and there are essentially 2 groups, those who know how to send email >> and those who complain about it. A solution was agreed on by nearly all >> of the contributors. It would be awesome to have a git-to-email proxy, >> such that you could do a git push <proxy> master:refs/for/mailinglist >> and this proxy would convert the push into sending patch series to the >> mailing list. It could even convert the following discussion back into >> comments (on Github?) but as a first step we'd want to try out a one >> way proxy. >> >> Unfortunately nobody stepped up to actually do the work, yet :( > > > 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/
Wow!!!
I will make sure to test it with a couple of patches I want to submit anyway.
Thanks so much! Dscho