Lines Matching refs:to

29 Then submit to the iperf3 issue tracker on GitHub:
33 **Note:** Issues submitted to the old iperf3 issue tracker on Google
34 Code (or comments to existing issues on the Google Code issue tracker)
40 New options (not necessarily complete, please refer to the manual page
46     -O, --omit N              omit the first n seconds (to ignore slowstart)
50     -k, --blockcount #[KMG]   number of blocks (packets) to transmit (instead
60 Deprecated flags (currently no plans to support)::
64     -T, --ttl                time-to-live, for multicast (default 1)
69 Also deprecated is the ability to set the options via environment
76 interest to a large fraction of users or have high impact for some
80 to solve the problem are currently being made:
82 * The ``-Z`` flag sometimes causes the iperf3 client to hang on OSX.
86   the Linux kernel automatically doubles the value passed in to
89   to the doubled value, but only to about 75% of the doubled
94   size, it is also used to set the socket buffer size.  This has been
95   shown to be helpful with high-bitrate UDP tests.
98   Linux), it might be necessary to invoke ``ldconfig`` manually after
103   correctly reflect the client-side measurements.  This is due to the
109   packets.  This issue is due to an artifact of timing between the
133 1. Update the ``README`` and ``RELEASE_NOTES`` files to be accurate. Make sure
135    are up to date.
142    status`` emits no output), make the changes necessary to produce
149     git commit -a      # commit changes to the local repository only
151     git commit -a      # commit changes to the local repository only
153     # Assuming that $VERSION is the version number to be released...
165 4. Stage the tarball (and a file containing the SHA256 hash) to the
185    allows a signed release announcement to be resent via email or sent
189     finalized.  To commit the release-engineering-related changes to
193      git push --tags     # Push the new tag to the GitHub repo
195 11. Send the PGP-signed release announcement to the following
196     addresses.  Remember to turn off signing in the MUA, if
197     applicable.  Remember to check the source address when posting to
211     due to Thunderbird trying to wrap the length of extremely long
212     lines (such as the SHA256 hash).  Apple Mail and mutt seem to
214     sending process by sending a copy to oneself first and attempting
215     to verify the signature is highly encouraged.
218     to announce the new release (see ``docs/news.rst`` and
220     documentation to GitHub Pages.
222 13. If an update to the on-line manual page is needed, it can be