Re: Patchy email

[David Kastrup]

David Kastrup <address@hidden> writes:

> David Kastrup <address@hidden> writes:
>
>> fatal: Not a valid object name master
>>
>> Apparently, the patch from
>> commit 7583351fbf2f08a4d1f3f0b075fe8b691adc0b95
>> Author: Knut Petersen <address@hidden>
>> Date:   Sun Jul 7 13:16:05 2019 +0200
>>
>>     Optimize tree.gittxt messages
>>     
>>     We display BRANCH, HEAD, MERGE-POINT
>>     and HISTORY fom merge-point to HEAD.
>>     
>>     If we do not find a merge-point we
>>     display the last ten commits if this
>>     is possible.
>>
>> relies on the existence of a local (rather than upstream) branch
>> "master", not a good idea.  I am backing out this commit from staging:
>> it needs to get fixed.
>
> Someone or some patchy happening to have a local master branch (a bad
> idea since absolutely no development should happen in a local master
> branch in our setup) already pushed that commit to staging.

I mean, to master.  Pushing to staging was very much the correct step to
take in the life of the patch.

> Consequentially, I had to push a revert to staging and hope I'll get it
> through without manually tampering with master.

-- 
David Kastrup