git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: git@vger.kernel.org
Cc: vegard.nossum@oracle.com
Subject: Making GitGitGadget conversion lossless
Date: Wed, 26 Feb 2020 15:09:29 -0500	[thread overview]
Message-ID: <20200226200929.z4aej74ohbkgcdza@chatter.i7.local> (raw)

Hi, all:

GitGitGadget is great, and I'm looking forward to adapting it to Linux 
Kernel's needs. There is one area where I think the situation can be 
further improved, and that's if the process of converting a pull request 
into a patch series were completely 100% reversible. As of right now, 
the following data is permanently lost from commits as they are 
converted into patches:

- parent/tree hashes
- author/committer information
- cryptographic attestation (gpgsig)

There is an existing body of work done by Vegard Nossum [1] that makes 
it possible to fully reconstruct a git commit from an email message, and 
I hope that it can make its way into official upstream. If that were to 
happen, it would mean that converting from a pull request into a patch 
series would become a lossless operation and tools like GitGitGadget 
would be able to preserve full cryptographic attestation of commits.

Vegard, if there is interest in getting this work into upstream, are you 
in a position to continue your work on it?

Best regards,
-K

[1]: https://lore.kernel.org/git/20191022114518.32055-1-vegard.nossum@oracle.com/#t


             reply	other threads:[~2020-02-26 20:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-26 20:09 Konstantin Ryabitsev [this message]
2020-02-26 21:01 ` Making GitGitGadget conversion lossless Junio C Hamano
2020-02-26 21:32   ` Vegard Nossum
2020-02-26 21:35   ` Konstantin Ryabitsev
2020-02-26 22:27     ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200226200929.z4aej74ohbkgcdza@chatter.i7.local \
    --to=konstantin@linuxfoundation.org \
    --cc=git@vger.kernel.org \
    --cc=vegard.nossum@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).