From: Benjamin Shefte Subject: Re: [PATCH] WBEMProxy: Implemented Complete SoftwareLicensingProduct row and data Message-Id: Date: Tue, 25 Jan 2022 17:37:23 -0600 In-Reply-To: References: <20220125141847.1186569-1-shefben@gmail.com> Does that mean just because no person has made an bugreport about it yet, it isn't needed now? and then in the future people with the issue will have to wait however many months for a full patch? seems a bit asinine and silly... Im thinking its time to fork wine into a less strict development enviroment where developers can code more freely not only deal with bugs releasted to games.. which linux shoulndt be used for anyway. On Tue, Jan 25, 2022 at 3:42 PM Marvin wrote: > Thank you for your contribution to Wine! > > This is an automated notification to let you know that your patch has > been reviewed and its status set to "Rejected". > > This means that the patch has been rejected by a reviewer. You should > have received a mail explaining why it was rejected. You need to fix > the issue and resend the patch, or if you are convinced that your > patch is good as is, you should reply to the rejection message with > your counterarguments. > > If you do not understand the reason for this status, disagree with our > assessment, or are simply not sure how to proceed next, please ask for > clarification by replying to this email. >
Does that mean just because no person has made an bugreport about it yet, it isn't needed now? and then in the future people with the issue will have to wait however many months for a full patch?

seems a bit asinine and silly... Im thinking its time to fork wine into a less strict development enviroment where developers  can code more freely not only deal with bugs releasted to games..  which linux shoulndt be used for anyway.

On Tue, Jan 25, 2022 at 3:42 PM Marvin <testbot@winehq.org> wrote:
Thank you for your contribution to Wine!

This is an automated notification to let you know that your patch has
been reviewed and its status set to "Rejected".

This means that the patch has been rejected by a reviewer. You should
have received a mail explaining why it was rejected. You need to fix
the issue and resend the patch, or if you are convinced that your
patch is good as is, you should reply to the rejection message with
your counterarguments.

If you do not understand the reason for this status, disagree with our
assessment, or are simply not sure how to proceed next, please ask for
clarification by replying to this email.