John Snow writes:
[...]
> (Random aside on patch submission process: I do dislike how when I
> change the topic of a commit, I lose out on git-backport-diff
> functionality. I wish I had a persistent ID for commits that survived
> beyond title changes. Sometimes I debate scripting adding some
On 4/16/21 2:17 AM, Markus Armbruster wrote:
John Snow writes:
On 4/15/21 3:00 AM, Markus Armbruster wrote:
John Snow writes:
On 3/30/21 1:18 PM, John Snow wrote:
Realizing now that this commit topic is wrong :)
A prior version modified the assertion, I decided it was less churn to
John Snow writes:
> On 4/15/21 3:00 AM, Markus Armbruster wrote:
>> John Snow writes:
>>
>>> On 3/30/21 1:18 PM, John Snow wrote:
>>>
>>> Realizing now that this commit topic is wrong :)
>>>
>>> A prior version modified the assertion, I decided it was less churn to
>>> simply add one.
>>>
>>>
On 4/15/21 3:00 AM, Markus Armbruster wrote:
John Snow writes:
On 3/30/21 1:18 PM, John Snow wrote:
Realizing now that this commit topic is wrong :)
A prior version modified the assertion, I decided it was less churn to
simply add one.
I think ideally we'd have no assertions here and we'd
John Snow writes:
> On 3/30/21 1:18 PM, John Snow wrote:
>
> Realizing now that this commit topic is wrong :)
>
> A prior version modified the assertion, I decided it was less churn to
> simply add one.
>
> I think ideally we'd have no assertions here and we'd rely on the type
> hints, but I
On 3/30/21 1:18 PM, John Snow wrote:
Realizing now that this commit topic is wrong :)
A prior version modified the assertion, I decided it was less churn to
simply add one.
I think ideally we'd have no assertions here and we'd rely on the type
hints, but I don't think I can prove that this
