From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Philip Oakley" Subject: Re: [Announce] submitGit for patch submission (was "Diffing submodule does not yield complete logs") Date: Fri, 22 May 2015 18:14:51 +0100 Organization: OPDS Message-ID: <0B3203305DF54249930E5903864B4988@PhilipOakley> References: <73db761f3c737965f64ac45005f7a716@www.dscho.org> <5b4bab2727a9fcee3a07724c64752cf9@www.dscho.org> Reply-To: "Philip Oakley" Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit Cc: "Stefan Beller" , "Robert Dailey" , "Heiko Voigt" , "Jens Lehmann" , "Git" , "Thomas Ferris Nicolaisen" , , "Johannes Schindelin" To: "Roberto Tyley" X-From: git-owner@vger.kernel.org Fri May 22 19:15:24 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 1YvqXY-0007Hu-Rj for gcvg-git-2@plane.gmane.org; Fri, 22 May 2015 19:15:21 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1946130AbbEVRPQ (ORCPT ); Fri, 22 May 2015 13:15:16 -0400 Received: from out1.ip05ir2.opaltelecom.net ([62.24.128.241]:63446 "EHLO out1.ip05ir2.opaltelecom.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1946028AbbEVRPP (ORCPT ); Fri, 22 May 2015 13:15:15 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2CsEADtY19VPJBLFlxcgxBUXoc6vRwfBoVxBAQCgTpNAQEBAQEBBwEBAQFBJBtBA4NZBQEBAQEDAQIFAQEdER4BARAGCwsCAwUCAQMVAwkaCxQBBAgHCwYHAxQGEwgCAQIDAQqHfAMWCbY9mDYNhHIBCxwEizqBPQGBD4FVEAIBUIMegRYFjAaGfHmDPIQdYoMBjnyDKINZgjokgT49MYJHAQEB X-IPAS-Result: A2CsEADtY19VPJBLFlxcgxBUXoc6vRwfBoVxBAQCgTpNAQEBAQEBBwEBAQFBJBtBA4NZBQEBAQEDAQIFAQEdER4BARAGCwsCAwUCAQMVAwkaCxQBBAgHCwYHAxQGEwgCAQIDAQqHfAMWCbY9mDYNhHIBCxwEizqBPQGBD4FVEAIBUIMegRYFjAaGfHmDPIQdYoMBjnyDKINZgjokgT49MYJHAQEB X-IronPort-AV: E=Sophos;i="5.13,476,1427756400"; d="scan'208";a="592887124" Received: from host-92-22-75-144.as13285.net (HELO PhilipOakley) ([92.22.75.144]) by out1.ip05ir2.opaltelecom.net with ESMTP; 22 May 2015 18:14:49 +0100 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: From: "Johannes Schindelin" > Hi Roberto, > > 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. -- Philip