<div class="gmail_quote">On Fri, Jun 26, 2009 at 4:17 PM, Ian Monroe <span dir="ltr"><<a href="mailto:ian@monroe.nu">ian@monroe.nu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Just an update with this: gitorious doesn't ban forced pushes, so</div>
someone could inadvertently screw up the repo in a non-revertible<br>
fashion fairly easily. </blockquote><div><br></div><div>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.</div>
<div> </div><div>Only a nitpick, though. I would also wait with this. If someone fucked up, someone with good git knowledge needs to fix it right away so other developers will be put on hold (at least from pushing/fetching).</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">So the project is on indefinite hold again. :(<br></blockquote></div><div><br></div>:-(<br clear="all">
<br>-- <br>Magnus Bergmark - magnus DOT bergmark AT gmail DOT com<br>GPG/PGP: 0x7BE84794DB6AA648<br>Fingerprint: 0E6F D2DB F0EF 534A 2184 52AF 7BE8 4794 DB6A A648<br>