<br><font size=2 face="sans-serif">take me off your mailing list!</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Robby Workman <rworkman@slackbuilds.org></b>
</font>
<br><font size=1 face="sans-serif">Sent by: slackbuilds-users-bounces@slackbuilds.org</font>
<p><font size=1 face="sans-serif">05/15/2008 01:39 PM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
"SlackBuilds.org Users List" <slackbuilds-users@slackbuilds.org></font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">"SlackBuilds.org Users List"
<slackbuilds-users@slackbuilds.org></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [Slackbuilds-users] "orphaned"
scripts</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>Phillip Warner wrote:<br>
> I would hope that all the script maintainers are a part of this mailing
<br>
> list, but I think that that would be a poor assumption. In light
of <br>
> that, perhaps it would be helpful to automatically add the maintainers
<br>
> email to a mailing list when they submit a script. I do not
mean this <br>
> list, but rather one that is to be used only occasionally.<br>
> <br>
> For instance, when the next version of Slackware is about to be released
<br>
> an email is usually sent to this list to let us know what that the
<br>
> repository will be rolling over soon and there are some changes to
the <br>
> new Slackware version that may break ___ type of scripts. This
one time <br>
> email per Slackware release could be sent to all the maintainers via
<br>
> this special mailing list. This would remind maintainers that
they are <br>
> maintainers, and to let them know that if they haven't done so recently
<br>
> they should take a look at their script to see if it is still up to
date <br>
> and compatible.<br>
<br>
<br>
Yeah, we had discussed doing that quite some time ago, but never<br>
reached a real consensus. I'm not too keen on unrequested mailing<br>
list subscriptions, so that's a point of contention, but otherwise,<br>
I agree that the idea is not a bad one.<br>
<br>
-RW<br>
_______________________________________________<br>
Slackbuilds-users mailing list<br>
Slackbuilds-users@slackbuilds.org<br>
</font></tt><a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users"><tt><font size=2>http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users<br>
Archives - </font></tt><a href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/"><tt><font size=2>http://lists.slackbuilds.org/pipermail/slackbuilds-users/<br>
FAQ - </font></tt><a href=http://slackbuilds.org/faq/><tt><font size=2>http://slackbuilds.org/faq/<br>
<br>
</font></tt></a></a></a>
<br>