impeding move to git, join gitorious.org

[Ian Monroe]

On Sat, Jun 27, 2009 at 3:22 AM, Magnus
Bergmark<magnus.bergmark at gmail.com> wrote:
> On Fri, Jun 26, 2009 at 4:17 PM, Ian Monroe <ian at monroe.nu> wrote:
>>
>> Just an update with this: gitorious doesn't ban forced pushes, so
>> someone could inadvertently screw up the repo in a non-revertible
>> fashion fairly easily.
>
> Nitpick: Not "non-reverstible", but "hard and error prone to revert to how
> we want it to be". Git takes special care *not* to delete any data, and a
> forced push does not delete data, only moves the pointer of the data. Using
> git reflog right after the pull (when you notice it's been borked) you
> should be able to revert by following standard procedures. AFAIK, that is.

Even someone doing a new clone could recover from a force push that
squashed a bunch of history or something? I kinda doubt it.

Undoubtedly its not so hard to recover from something if someone
realizes whats going on and fixes it. But I think a SCM should be 100%
lossless.

Ian