Re: GURU contributions

On Tue, Jun 16, 2026 at 12:15=E2=80=AFAM Alexis <[email protected]> wrot=
e:
>
> Ben Knoble <[email protected]> writes:
>
> > I found the Wiki a bit unclear; is the best way to send a patch
> > (or more than one) to GURU to file a bug on b.g.o.?
> >
> > It sort of seemed like the only contribution process was to
> > request
> > access (via bug), then push to the develop branch and wait for
> > review
> > to pick to the main trunk.
> >
> > I might eventually be interested in contributing like that one
> > day, but for a one-off (and relatively trivial) patch, it seems
> > like overkill.
>
> *nod* Yeah.
>
> Based on my own experience when working with the _Gentoo_ repo,
> and because GURU bugs in general should be reported on b.g.o, i
> would suggest using format-patch to create a patch (including
> Signed-off-by) for b.g.o. To give you an idea, here's my most
> recent patch:
>
>   https://bugs.gentoo.org/975941

Yeah, that's pretty much what I'd resigned myself to doing. Thanks!

> (i keep a local copy of the Gentoo repo around, which i pull
> before creating any patches, then create a new branch for
> development of a particular patch, so that i can have multiple
> patches on the go at once if necessary.)

More or less ditto :) but since the Gentoo repo is a little more
forge-friendly in terms of how contributions are accepted,
branch-per-contribution becomes a requirement. For something like what
I have in mind, and where format-patch is accepted, committing
directly to a local trunk branch or even on detached head is fine :P
since I can control what to format-patch out.

--=20
D. Ben Knoble