On Tuesday, 19 May 2015, Stefan Beller <sbel...@google.com> wrote: > On Tue, May 19, 2015 at 12:29 PM, Robert Dailey > <rcdailey.li...@gmail.com> wrote: > > How do you send your patches inline? > > 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 :(
I've replied to this on a separate announcement thread on the Git mailing list here: http://thread.gmane.org/gmane.comp.version-control.git/269699 ...I've created a new tool called submitGit, which aims to help. > > I am willing to review the typical workflow for contributing via git > > on mailing lists but I haven't seen any informative reading material > > on this. I just find using command line to email patches and dealing > > with other issues not worth the trouble. Lack of syntax highlighting, > > lack of monospace font, the fact that I'm basically forced to install > > mail client software just to contribute a single git patch. I'd be interested to know what you think! Roberto -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
