The Git history is source code too. Reading and comprehending is key.
We spend as much or more time reading Git logs as building new ones.

FWIW (not much) I would prefer a few minutes grace period where people
can push --force, rather than a tangled git history conveying no
information except that somebody made an error.

On Sun, Feb 5, 2012 at 10:05 AM, Paul Davis <[email protected]> wrote:
> Noah managed to merge 1.2.x to itself. I caught it in a few minutes so
> made a snap decision and fixed it. I plan on fixing up the hooks
> tomorrow to prevent it from happening again.
>
> On Sun, Feb 5, 2012 at 3:00 AM, Paul Davis <[email protected]> 
> wrote:
>> This is not the commit you are looking for.
>>
>> On Sun, Feb 5, 2012 at 1:32 AM, Randall Leeds <[email protected]> 
>> wrote:
>>> What happened here? Why forced?
>>>
>>> On Fri, Feb 3, 2012 at 14:04,  <[email protected]> wrote:
>>>> Updated Branches:
>>>>  refs/heads/1.2.x 05a6aea97 -> 506deab47 (forced update)



-- 
Iris Couch

Reply via email to