Problem reporting (was 1.5.21-1: CIFS symlinks on network share break Cygwin)

[Larry Hall (Cygwin)]

Christopher Faylor wrote:
> On Wed, Oct 25, 2006 at 03:07:19PM -0500, DePriest, Jason R. wrote:
>> On 10/25/06, DePriest, Jason R. <> wrote:
>>> 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.
>> sorry patch in wrong format... subject changes since I am severely
>> hijacking this topic
> 
> Sorry Jason (and Larry) but I really don't see how this is appropriate
> for the problems.html page.  This is just a general good practice for
> sending email.  The problems.html page already has enough ignored advice
> that I doubt that adding this would be of much help.



I certainly agree that it's good practice but it's also pretty clear that
we have a number of posters who aren't aware of it.  I don't expect that
having this information as part of the problem reporting guidelines will
dramatically reduce the occurrence of these problems but it would provide
us a convenient place to point to for these infractions and also help with
the "well I didn't see that stated anywhere" cases.  There may even be the
occasional person that actually does read the whole page who will not
only feel well-informed about our list etiquette but also will be. ;-)

OK, I feel like I'm stating the obvious here so I won't take up anymore
bandwidth. :-)


-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746

--
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/