<div dir="ltr"><div class="gmail_default" style="font-size:x-small">hi Chris,</div><div class="gmail_default" style="font-size:x-small"><br></div><div class="gmail_default" style="font-size:x-small">I suppose there has been a misunderstanding as nothing changed in our general policy.</div><div class="gmail_default" style="font-size:x-small"><br></div><div class="gmail_default" style="font-size:x-small">Matteo<br></div><div class="gmail_default" style="font-size:x-small"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Il giorno ven 3 giu 2022 alle ore 01:19 Christoph Willing <<a href="mailto:chris.willing@linux.com">chris.willing@linux.com</a>> ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I just noticed one of the SlackBuilds that I maintain sitting in the<br>
pending queue even though I'd made no changes.<br>
<br>
When discussing this with the person who made the submission, pointing<br>
out the need to first contact the maintainer, they said that:<br>
"I've gotten some different advice from one of the admins for certain<br>
situations"<br>
<br>
Is this a new policy - that "for certain situations" anyone can<br>
arbitrarily submit changes for a SlackBuild?<br>
<br>
<br>
chris<br>
_______________________________________________<br>
SlackBuilds-users mailing list<br>
<a href="mailto:SlackBuilds-users@slackbuilds.org" target="_blank">SlackBuilds-users@slackbuilds.org</a><br>
<a href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" rel="noreferrer" target="_blank">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
Archives - <a href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/" rel="noreferrer" target="_blank">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
FAQ - <a href="https://slackbuilds.org/faq/" rel="noreferrer" target="_blank">https://slackbuilds.org/faq/</a><br>
<br>
</blockquote></div>