git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: publish from certain commit onward, keeping earlier history private, but provable

From
Jeff King <peff@peff.net>
Date
Dec 9, 2015, 22:24 UTC
Message-ID
<20151209222412.GC21751@sigill.intra.peff.net>
In-Reply-To
<20151209222041.GB21751@sigill.intra.peff.net>
On Wed, Dec 09, 2015 at 05:20:41PM -0500, Jeff King wrote:
> Of course that is a bitter pill to swallow if you have reasons for
> wanting to use the old sha1s. E.g., you have internal development
> proceeding against the old tree and want to share a truncated version
> with the public.

After re-reading your email, it looks like your use case is just to be able to later prove the existence of the original history. You could that by mentioning the original "C" in your truncated "D", but in a way that git does not traverse reachability. For instance, amend D's commit message to say:

  This is based on earlier, unpublished work going up to commit C.

Then retain C for yourself, and show it only to those you want to prove its contents to.

-Peff
Previous: Jeff KingNext: Stefan Beller
Message 4 of 6 in “publish from certain commit onward, keeping earlier history private, but provable”
  1. Jörn HeesDec 9, 2015
  2. Johannes LöthbergDec 9, 2015
  3. Jeff KingDec 9, 2015
  4. Jeff KingDec 9, 2015
  5. Stefan BellerDec 9, 2015
  6. Jeff KingDec 9, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.