Hi Doug,
Some comments on the actual mechanics here (vs. on the kernel list I
picked this up from).
It seems like perhaps you could increase the "count" variable. You got:
20190828132723.0.RFC.Ie6289f437ae533d7fcaddfcee9202f0e92c6b2b9@changeid
but usually patches are numbered starting from 1, n
Hi,
On Wed, Aug 28, 2019 at 2:05 PM Johannes Berg wrote:
>
> Hi Doug,
>
> Some comments on the actual mechanics here (vs. on the kernel list I
> picked this up from).
>
> It seems like perhaps you could increase the "count" variable. You got:
>
> 20190828132723.0.RFC.Ie6289f437ae533d7fcaddfcee920
As per the centithread on ksummit-discuss [1], there are folks who
feel that if a Change-Id is present in a developer's local commit that
said Change-Id could be interesting to include in upstream posts.
Specifically if two commits are posted with the same Change-Id there's
a reasonable chance that
3 matches
Mail list logo