Στις Παρ, 11 Δεκ 2020 στις 11:00 μ.μ., ο/η Segher Boessenkool < seg...@kernel.crashing.org> έγραψε:
> On Fri, Dec 11, 2020 at 10:16:44PM +0200, abebeos wrote: > > Στις Παρ, 11 Δεκ 2020 στις 10:02 μ.μ., ο/η Segher Boessenkool < > > seg...@kernel.crashing.org> έγραψε: > > > > My understanding of "non-FSF world-legals" is that something that is > > > > already released/assigned needs no submission. > > > > > > It's not just that: all patches should hit gcc-patches@. For > > > transparency, and so that everyone can easily comment on it. > > > > > > If someone has published a modified GCC anywhere public, anyone can > > > take that code. That is how the GPL works. > > > > > > But we still need it on gcc-patches to review it :-) > > > > Ok, to speed things up, is it ok if I simply pick the patch that I've > > attached to the issue: > > > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729#c21 > > I see no patch attached there? Just a link to github. > sorry, it's on top of the issue. direct link: https://gcc.gnu.org/bugzilla/attachment.cgi?bugid=92729&action=viewall > > > and post it here to the gcc-patches list within at [PATCH] tagged new > topic? > > Yes, all patches should always be a new thread. Multiple versions of a > series in one thread is much harder to work with then necessary; and a > patch somewhere deep in a thread is easily lost or overlooked. > ok > I'd ask the original author, but it seems he's busy with other work, so to > > avoid delays... > > Please try to ask him first? That is always nice, contacted days ago both authors via email (naturally closing with "feel free to ignore if you're busy"), pip replied, saa not. Though both are on the cc of the issue, too. > but you all also need to figure out what to do with the bounty. > Yes, the final "drama", but in the end, the bounty-backers decide about any claims. If they e.g. decide to hand out the bounty to the patch-producer... well. Me currently anyways more in "want to get this done" (before my attention window closes). Segher >
