https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729
--- Comment #40 from abebeos at lazaridis dot com ---
(In reply to John Paul Adrian Glaubitz from comment #39)
> (In reply to abebeos from comment #38)
> > Can someone please ping gcc-patches (me having troubles setting up email
> > alias on gmail, don't want to use my main email)
>
> I'm not sure what you are trying to achieve.
Naturally, at this point, that someone verifies my results (I made this as
simple as a few cli commands).
> There are guidelines for submitting patches which include signing the FSF
> copyright assignment using your full name and a proper email address.
No need for full-name in public (FSF accepts even pseudonyms), no need to sign
anything just to get a technical feedback ("review"). We are now in "review"
state.
> It's not possible to merge patches anonymously and it's also not possible to
> claim a bounty for the work contributed by a third party.
I spend nearly a full-(over)-time month to achieve a result, fighting through
incomplete/inconsistent/missing documentation and "dark land", providing
finally the necessary (mostly) integration work. If I reuse existing code
instead of writing from scratch, well, I think that's the original authors
decision how to handle this.
But please stop talking like I did nothing, that's simply rude.
> An example for the proper process for submission of such a patch can be
> found here:
>
> > https://gcc.gnu.org/pipermail/gcc-patches/2020-November/559698.html
Too much talk for my taste. Test-suites talk better.
And if i need a lawyer to just be able to claim a bounty, well...
The thing is: can someone please verify the test-results?