Reporting context with list submittals for defects when local git branches are involved: needs a new description?

Ulrich Spörlein uqs at freebsd.org
Mon Jan 4 19:46:39 UTC 2021


On Mon, 2021-01-04 at 09:27:10 -0800, Mark Millard wrote:
>On 2021-Jan-4, at 08:28, Ulrich Spörlein <uqs at freebsd.org> wrote:
>>
>> I'm a bit confused as to what you are asking here, tbh. Are you working on a branch of your own? In that case, a bug report needs to have some concrete pointers to what you've changed locally, or you need to revert to a clean tree or something.
>
>Old PowerMacs do not work sufficiently based on pure FreeBSD. But my
>workarounds are genrally not sufficient for committing either. (powerpc
>is the primary context that lead to me having some patches. I'll use it
>for illustration.) Many problems have nothing to do with what I've
>patched. When I can, I instead report based on instead using
>artifact.ci.freebsd.org material and its behavior, but some bugs do not
>show up in debug builds or the PowerMac support problems make this not
>work.
>
>In complicated cases that allowed it, I've reported both from using
>artifact.ci.freebsd.org material and from using my patched context,
>in part demonstrating that a problem exists in both but providing
>additional evidence.
>
>> Or do you just want to have some minor things modified on your tree?
>
>That would probably be a reasonable view of my patches accumulated over
>the years, patches that I bring forward as I go. Adding a new one is
>fairly rare.
>
>> In that case, maybe using git stash and git rebase --autostash would suit you better?
>
>A possibility, but I'm exploring alternatives. git is likely to lead to
>more people having local branches involved in how they choose to operate.
>That in turn may lead to more reports based on such contexts. My exploring
>may be an early warning.

Ah, sorry for being dense earlier. You are correct in pointing out that 
it might get a bit harder to see from problem reports what exact version 
a user was running.

I feel that typically we ask of users to upgrade to latest current or 
stable anyway before reporting bugs, so just the information that they 
are somewhat up to date is usually good enough. But we might have to do 
something smarter in the future, indeed.

Thanks!
Uli


More information about the freebsd-git mailing list