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

Re: Making git history strictly time safe

From
Andrew Ardill <andrew.ardill@gmail.com>
Date
May 18, 2012, 01:49 UTC
Message-ID
<CAH5451mwy51DjNM49ywDX5XHyLNMJSKk_NGiiQwydjgqyBzcNw@mail.gmail.com>
In-Reply-To
<2EDEF5ABBE208442B7547C8D36B9D8840C4A04@nawespscez09v.nadsuswe.nads.navy.mil>

On 18 May 2012 01:51, Jones, Brian P CTR SPAWARSYSCEN-PACIFIC, 63600 <brian.p.jones4.ctr@navy.mil> wrote:

> Andrew,
>
> If I had a tag pointing to a commit that was so latter hidden could I easily return to the commit and say build it by referencing that tag without having to do any git magic?

Exactly, as long as the tag wasn't moved for some reason (it is quite hard to move tags, but not /impossible/).

If you wanted to be even more sure, you can write the sha-1 of the correct commit down on a piece of paper, and hide it in your wallet so no one is able to change it on you.

Of course, if you have a local checkout of the repository there is nothing forcing you to accept changes someone else has made. This is what the flags on the server do, automatically rejecting changes that rewrite history. There is nothing stopping someone rewriting their own history on their local repository, all we can do is control what we have, which is the server and your local copy.

In the end, as long as someone knows what the 'correct' reference is to the correct history, you won't lose anything.

Regards,
Andrew Ardill
Previous: Jones, Brian P CTR SPAWARSYSCEN-PACIFIC, 63600Next: Sitaram Chamarty
Message 4 of 5 in “Making git history strictly time safe”
  1. Jones, Brian P CTR SPAWARSYSCEN-PACIFIC, 63600May 16, 2012
  2. Andrew ArdillMay 17, 2012
  3. Jones, Brian P CTR SPAWARSYSCEN-PACIFIC, 63600May 17, 2012
  4. Andrew ArdillMay 18, 2012
  5. Sitaram ChamartyMay 18, 2012

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.