<br><br><div class="gmail_quote"><div dir="ltr">On Sun, Mar 5, 2017, 3:10 AM Willy Sudiarto Raharjo <<a href="mailto:willysr@slackbuilds.org">willysr@slackbuilds.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> I've always wondered about this. Wouldn't it be easier for the<br class="gmail_msg">
> maintenance team to deal with _some_ form of version control, rather<br class="gmail_msg">
> than updated archives delivered through <a href="http://slackbuilds.org" rel="noreferrer" class="gmail_msg" target="_blank">slackbuilds.org</a>?<br class="gmail_msg">
<br class="gmail_msg">
We do have and we used git<br class="gmail_msg">
<br class="gmail_msg">
see the web-based interface here:<br class="gmail_msg">
<a href="https://slackbuilds.org/cgit/slackbuilds" rel="noreferrer" class="gmail_msg" target="_blank">https://slackbuilds.org/cgit/slackbuilds</a></blockquote></div><div><br></div><div>Do you prefer one method over another?</div><div><br></div><div>Jeremy</div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class="gmail_msg">
</blockquote></div>