Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 16 Oct 2019 10:45:19 -0400
From:   Santiago Torres Arias <santiago@nyu.edu>
To:     Willy Tarreau <w@1wt.eu>
Cc:     Vegard Nossum <vegard.nossum@oracle.com>,
        workflows@vger.kernel.org, Git Mailing List <git@vger.kernel.org>,
        LKML <linux-kernel@vger.kernel.org>,
        Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
        Eric Wong <e@80x24.org>
Subject: Re: email as a bona fide git transport
Message-ID: <20191016144517.giwip4yuaxtcd64g@LykOS.localdomain>
References: <b9fb52b8-8168-6bf0-9a72-1e6c44a281a5@oracle.com>
 <20191016111009.GE13154@1wt.eu>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
        protocol="application/pgp-signature"; boundary="mrjm34jdre4iu7ux"
Content-Disposition: inline
In-Reply-To: <20191016111009.GE13154@1wt.eu>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


--mrjm34jdre4iu7ux
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Willy, Vegard.

On Wed, Oct 16, 2019 at 01:10:09PM +0200, Willy Tarreau wrote:
> Hi Vegard,
>=20
> On Wed, Oct 16, 2019 at 12:22:54PM +0200, Vegard Nossum wrote:
> > (cross-posted to git, LKML, and the kernel workflows mailing lists.)
> >=20
> > Hi all,
> >=20
> > I've been following Konstantin Ryabitsev's quest for better development
> > and communication tools for the kernel [1][2][3], and I would like to
> > propose a relatively straightforward idea which I think could bring a
> > lot to the table.
> >=20
> > Step 1:
> >=20
> > * git send-email needs to include parent SHA1s and generally all the
> >   information needed to perfectly recreate the commit when applied so
> >   that all the SHA1s remain the same
> >=20
> > * git am (or an alternative command) needs to recreate the commit
> >   perfectly when applied, including applying it to the correct parent
> >=20
> > Having these two will allow a perfect mapping between email and git;
> > essentially email just becomes a transport for git. There are a lot of
> > advantages to this, particularly that you have a stable way to refer to
> > a patch or commit (despite it appearing on a mailing list), and there
> > is no need for "changeset IDs" or whatever, since you can just use the
> > git SHA1 which is unique, unambiguous, and stable.

I wonder if it'd be also possible to then embed gpg signatures over
send-mail payloads so as they can be transparently transferred to the
commit.

-Santiago

--mrjm34jdre4iu7ux
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEkDurc2QOttZVM+/zRo8SLOgWIpUFAl2nLP0ACgkQRo8SLOgW
IpUWCQ//UFA5stuXzMxzWIKHQD+H0TuHkdaljhkWkD/PJkKg38VK0qyxCwqszoVd
wRfV3HZa/hoPkY6pnoqIm+VfqbuEnZ5K93I7mGvsKnY9lAOh7GXYjETV62XN0sT7
goQPqxoBM+a9hEBYSccYARaq2EGmDHojhEYJjLIR2br4XXMn+Mrd0VQ90Kph2ozn
WwwoBeqNQaA2gH2fBeYmWKfpuY+0yIRxQfX2gflOx7IDVQAm9NiPqV2FakfZ5Kq8
W8QhGRIpDvIIzmqpGpuETPBtXt/eABENOyoa+E8iFviEM471N6ww3PVQAD6ZJ9k+
LofGz4XhiNOgAHWRKIh4v6zYZgxXfXtIojAZLDR2TGSrfWDj4l9EJ0nNNI2pYspV
1xFkCYEUwoLORs1BLo1Zn2mO4XhiAcsQvrJwRdHvT6MFDDOl59SpQQkCJ77udupr
oCwHoJ4Ew/zHn8y+H7PRoNc9cIqhIUbBTqSJ9lNczOjOaliSBGDQ46CsEfEoT2eT
hxtkOiZQBpLKifJ9oPxGKqD1yPRFI+mNYCkye/yx7BN8Mgo/wqei4ypu+pmdpai8
LF41nXT1flRHt/ffTJSUP4JqpJXH96Kkz+PCUsBQ3x6zf0eMQNaVY59lXdXN44Wy
TYRbjZx4va+x+wkmRl6Z+7WefkAqrL3H2l6XjBvTkXYfZneLuGg=
=LpIO
-----END PGP SIGNATURE-----

--mrjm34jdre4iu7ux--