Re: Making git history strictly time safe

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 18 May 2012 01:51, Jones, Brian P CTR SPAWARSYSCEN-PACIFIC, 63600
<brian.p.jones4.ctr@xxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]