to see if the problem is already known. Also, there are several patches for
being-considered features in the <a href="/ftp/unpacked/rsync/patches/">patches dir</a>.
-<p> Also, please take a couple of minutes to read Simon Tatham's
+<p> If you haven't already done so, please take a couple of minutes to read Simon Tatham's
<a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">advice
on how to report bugs</a>.
<ul>
-<li> The preferred method is to
+<li> Your primary resource is the
+<a href="http://lists.samba.org/mailman/listinfo/rsync">rsync mailing list</a>
+which is at <tt>rsync@lists.samba.org</tt>. Use this list to discuss any
+problem you're seeing or enhancements you're thinking of and get help/responses
+from your fellow rsync users and those working on it. The mailing list does
+accept patches (typically as MIME attachments), but it is often easier to
+attach a patch to an appropriate bugzilla report.
+
+<li> If you'd like to see a bug-report or feature-request get officially noted,
<a href="https://bugzilla.samba.org/enter_bug.cgi?product=rsync">create a
report via bugzilla</a> (this does require that you have created a bugzilla
-account, but that is a very simple process). Set <code>Severity</code> to
-<code>Enhancement</code> <b>if</b> you're making a suggestion.
-
-<li> Alternately, you can send an email to the
-<a href="http://lists.samba.org/mailman/listinfo/rsync">rsync
-mailing list</a>, which is at <tt>rsync@lists.samba.org</tt>. You
-can send patches to the list as well.
+account, but that is a very simple process). All new items and changes to
+existing items generate email to the mailing list, so the list naturally stays
+up-to-date with what is happening in the bug-tracking database.
</ul>
git.samba.org / rsync-web.git / blobdiff