[Slackbuilds-users] New policy or poor advice?

[David Chmelik]

Someone pushed a patch for previous rogue.tar.gz version on GitHub.com, 
which I don't (and won't) even use for my SlackBuilds.  I only found out 
when sbopkg & sbotools said Rogue was already updated on SBo without me 
having updated Rogue.  I didn't obscure/anti-spam my email in rogue.info 
nor was inactive--in fact was aware of the problem because of testing my 
builds on Slackware-current--perhaps people were just catching up after 
Slackware 15.  I thanked the person for patch but asked them in future 
to email first.

On 6/3/22 1:20 AM, Matteo Bernardini wrote:
> hi David,
>
> could you please detail when and how this happened so we could try to 
> give an answer?
>
> Matteo
>
> Il giorno ven 3 giu 2022 alle ore 10:08 David Chmelik 
> <davidnchmelik at gmail.com <mailto:davidnchmelik at gmail.com>> ha scritto:
>
>     It happened to me once also.  A patch was needed, but the person who
>     submitted it didn't even try to contact me, so didn't know I was also
>     updating to newer source code that didn't need the patch.
>
>     On 6/3/22 12:59 AM, Matteo Bernardini wrote:
>     > hi Chris,
>     >
>     > I suppose there has been a misunderstanding as nothing changed
>     in our
>     > general policy.
>     >
>     > Matteo
>     >
>     >
>     > Il giorno ven 3 giu 2022 alle ore 01:19 Christoph Willing
>     > <chris.willing at linux.com <mailto:chris.willing at linux.com>
>     <mailto:chris.willing at linux.com <mailto:chris.willing at linux.com>>>
>     ha scritto:
>     >
>     >     I just noticed one of the SlackBuilds that I maintain
>     sitting in the
>     >     pending queue even though I'd made no changes.
>     >
>     >     When discussing this with the person who made the
>     submission, pointing
>     >     out the need to first contact the maintainer, they said that:
>     >             "I've gotten some different advice from one of the
>     admins
>     >     for certain
>     >     situations"
>     >
>     >     Is this a new policy - that "for certain situations" anyone can
>     >     arbitrarily submit changes for a SlackBuild?
>     >
>     >
>     >     chris
>