From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Schindelin Subject: Re: [Announce] submitGit for patch submission (was "Diffing submodule does not yield complete logs") Date: Fri, 22 May 2015 21:58:19 +0200 Organization: gmx Message-ID: <93994cca5e27388aee7e7c5fd4508816@www.dscho.org> References: <73db761f3c737965f64ac45005f7a716@www.dscho.org> <5b4bab2727a9fcee3a07724c64752cf9@www.dscho.org> <0B3203305DF54249930E5903864B4988@PhilipOakley> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Roberto Tyley , Stefan Beller , Robert Dailey , Heiko Voigt , Jens Lehmann , Git , Thomas Ferris Nicolaisen , emma@gitforteams.com To: Philip Oakley X-From: git-owner@vger.kernel.org Fri May 22 21:58:33 2015 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Yvt5T-0000R4-Ve for gcvg-git-2@plane.gmane.org; Fri, 22 May 2015 21:58:32 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757385AbbEVT62 (ORCPT ); Fri, 22 May 2015 15:58:28 -0400 Received: from mout.gmx.net ([212.227.15.18]:59062 "EHLO mout.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756048AbbEVT61 (ORCPT ); Fri, 22 May 2015 15:58:27 -0400 Received: from www.dscho.org ([87.106.4.80]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0MYwVv-1YhyyE0Wvb-00Vcwa; Fri, 22 May 2015 21:58:21 +0200 In-Reply-To: <0B3203305DF54249930E5903864B4988@PhilipOakley> X-Sender: johannes.schindelin@gmx.de User-Agent: Roundcube Webmail/1.1.0 X-Provags-ID: V03:K0:Wkob0DOkH+RiZ4yVhYtzF1fuU6AMvUPnuPDS7b8driZ9EfjzRx+ c+iHzw0D/rMKncnjHIWvIrzmy2AXlVPVoSnLCiCPtb7OOhxsX6ecBAvBemUiojGTdn5zZ9Q aZv80OJuVulv5koz9c2BBI66lCJTtxeXDggTPGX7sfoOLchbPE4MFxcFDOfXu820mvFOGPt XfTHQtoB2DoPqawulTe5Q== X-UI-Out-Filterresults: notjunk:1; Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Hi, On 2015-05-22 19:14, Philip Oakley wrote: > From: "Johannes Schindelin" >> On 2015-05-22 11:42, Johannes Schindelin wrote: >> >>> On 2015-05-22 10:33, Roberto Tyley wrote: >>>> On Tuesday, 19 May 2015, Stefan Beller wrote: >>>>> On Tue, May 19, 2015 at 12:29 PM, Robert Dailey >>>>> 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 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. >> >> I just tried this with https://github.com/git/git/pull/139 and would like to tell you about two wishes I had immediately: >> >> - If the author of a patch I am submitting is not myself, could submitGit maybe add that `From: ` line at the top of the mail? >> - The patch series is sent without a cover letter, but it would be *really* great if a path series consisting of more than one patch could have the initial comment of the Pull Request as a cover letter, with the link to the original Pull Request at the bottom? This would also be the mail to use in the "In-reply-yo" header instead of the first patch. >> >> Thanks so much! >> Dscho > > > A separate request would be to be able to use PRs that are for forks > of git/git, such as msysgit etc. (i.e. have a common --root), which > would help in the upstreaming of some changes. > > > I ask because I just logged in and my preparatory PR318 > (https://github.com/msysgit/git/pull/318) for rejuvenating the > msvc-build system wasn't listed, probably because of the forking. You can easily change what upstream your PR is intended for. For example, I made my PR from my own Git fork (which is based on msysgit/git) relative to git/git by entering the URL: https://github.com/git/git/compare/next...dscho:non-win-fixes?expand=true So there is no real need for anything extra: the only git.git project that requires emails (that I am aware of) for the submission process is git/git. Ciao, Dscho