From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS8560 212.227.0.0/16 X-Spam-Status: No, score=-4.2 required=3.0 tests=AWL,BAYES_00,FREEMAIL_FROM, RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H2,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0 Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 7C0122018E; Wed, 24 Aug 2016 15:34:19 +0000 (UTC) Received: from virtualbox ([37.24.141.250]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0Ma2Lr-1brD9u0jAl-00LrHX; Wed, 24 Aug 2016 17:34:05 +0200 Date: Wed, 24 Aug 2016 17:34:02 +0200 (CEST) From: Johannes Schindelin X-X-Sender: virtualbox@virtualbox To: Arif Khokar cc: =?UTF-8?Q?Jakub_Nar=C4=99bski?= , Jeff King , Stefan Beller , "meta@public-inbox.org" , "git@vger.kernel.org" , Eric Wong Subject: Re: Working with public-inbox.org [Was: [PATCH] rev-parse: respect core.hooksPath in --git-path] In-Reply-To: Message-ID: References: <20160819150340.725bejnps6474u2e@sigill.intra.peff.net> <46a5b9b6-f3f6-7650-8a5b-b0b52223e375@gmail.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: multipart/mixed; BOUNDARY="8323329-2144075108-1472052845=:4924" X-Provags-ID: V03:K0:WBeb2wYPps9mpasleUqx/AztYu8F7CmwTiBD5ECcZ+TMoG6GzjT lJcg8CS2lHMbCmb8zyypVWKClJq45jUrq7ryNtZDL/CorrQFJjvZb9DZ7ruG8rZe0qbYHo2 KcDIJpgoVac77n7KPIWg6q1xO5stUVeNrPo0HM2a6V7IRgaMbioD9bxeNPQ4/GI4bJ7wVmA m3tyAGNbJfDxbtceBq8uw== X-UI-Out-Filterresults: notjunk:1;V01:K0:SA7Y/TxxMLQ=:mjrm6yQAuJws610+3r8LYg DHu8lDn4AFulaTxrejXZwMNZT00CtznFS8hEHoWf0CcKx9C49TgNAtecGKi4EDfItMj1YC45n UP1qmldf8Q2d/y0Ow6ZARLIVTGh9vH/QzSEYIasZVXndwKTaE5gbsfZ1QdHgfYOKnjdf4XMQV iqO9PUm2GtMMmVLM4LG23mZNWKVpUBFe/F49sD+nrrsqi5cy41CCLce1CTJEmM613vSUcvWpj eGA3jgAdETU82p+CGdYQCJ2fq1xgkMX5RGXnUCsUuS3pIuXg4zbzCR9EPcV+vfpKxP2TRCr5S Cazv+Avg/YQuFnKyLSKGzTB1HJRT/ImSJd9/qyQPyCgVwxXHUY0L6QWWgKiiSOHCTFBt6IV1B 0MPDmnoBKIBVr22Fc/A+rbIG/rxAXlrHtBiacJJaCJCqO/w4guCkSnvAL2X8A+x9lRM7BD5c6 Qh503It26d+cduai/bAHcwNVs7zAFtS8NEsl9cK4wPPxnTGugQ1yZ4o8o4N52aeCOD/xjjkHm fHQeqeYQAtxQNpQ5+vNhT5sotwcsdIw1ILyCOIgV0BuYOoIEDSEigE+ZC1l9aURk4NHIVnK9z 4gjPGmBaL2HY0W9RGtTrGayAl0YKLgMIhBb/ZGvYsciHnjkNVgMqszlxrdvdCOT4WlEwVH3J8 Mnobx7KE9UKRWDX60O3BoYy40q1ozx3OX3LZKCZ8vMLjV5NJHWUjoqr0MTj/x7qakDtbb/7uB 6MbyLy38tDHJZNdyq+tRAtvq2liewjShgIxsenZ7DSZ5WOffNWr2Rke3Egr5tRUqieJ8bTOeL ppCaSUJ List-Id: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-2144075108-1472052845=:4924 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Hi Arif, On Tue, 23 Aug 2016, Arif Khokar wrote: > On 08/20/2016 03:57 PM, Jakub Nar=C4=99bski wrote: >=20 > > But perhaps the problem is current lack of tooling in the opposite > > direction, namely getting patches from mailing list and applying them > > to GitHub repo, or Bitbucket, or GitLab. Though with working Git, it > > is something easier than sending patches via email; it is enough that > > email client can save email to a file (or better, whole sub-thread to > > file or files). >=20 > Given that public-inbox provides an NNTP interface, couldn't the ARTICLE > NNTP command be used to easily retrieve the messages in a > given patch series (at least compared to POP or IMAP). Perhaps > git-send-email could be modified to include the message-id value of each > patch in the series that it sends to the mailing list and include it in > the cover letter. I am no expert in the NNTP protocol (I abandoned News long ago), but if you go from HTML, you can automate the process without requiring changes in format-patch. > Then a script could be written (i.e., git-download-patch) which could > parse the cover letter message (specified using its message-id), and > download all the patches in series, which can then be applied using > git-am. This would in fact take the email client out of the equation in > terms of saving patches. I recently adapted an old script I had to apply an entire patch series given the GMane link to its cover letter: https://github.com/git-for-windows/build-extra/blob/master/apply-from-gmane= =2Esh Maybe you find it in you to adapt that to work with public-inbox.org? Ciao, Johannes --8323329-2144075108-1472052845=:4924--