1.5.21-1: CIFS symlinks on network share break Cygwin
DePriest, Jason R.
jrdepriest@gmail.com
Wed Oct 25 20:07:00 GMT 2006
On 10/25/06, Larry Hall (Cygwin) <> wrote:
> Certainly this and quoting raw email addresses could be offered as
> guidelines in <http://cygwin.com/problems.html>. Care to offer a
> patch
The "submitting a patch" guidelines seem to refer to program
patches... since this is only an HTML update, here it is.
-Jason
-------------- next part --------------
178a179,196
> <a name="etiquette">
> <li><p>When you respond to a report, you must remember to <em>include
> only what is relevant</em>.</p>
>
> <p>The contents of the original message or of any other responses are not sacred.
> Do not hesitate to trim out the extraneous parts as the full messages will still be
> available as either previously received emails or permantently in the archives.<br>
>
> <em>Avoid <a href="http://cygwin.com/acronyms/#TOFU">TOFU</a> entirely</em>.
> Putting your replies at the top of the message instead of inline where appropriate and
> leaving every single bit of the original message and all of the other replies and
> observations below makes for a very untidy archive. As was arleady mentioned, the
> original messages are still available. We don't need you wasting space and bandwidth
> because you couldn't be bothered to hit the DEL key a few times.</p>
>
> <p>In addition, please observe <a href="http://cygwin.com/acronyms/#PCYMTNQREAIYR">PCYMTNQREAIYR</a>
> as we are not in the habit of feeding Spam bots.</p></li>
>
-------------- next part --------------
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
More information about the Cygwin
mailing list