public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: nmehta <nmehta@cs.caltech.edu>
To: cygwin@cygwin.com
Subject: Re: cygwin makes shared folders on vista
Date: Sun, 14 Oct 2007 07:26:00 -0000	[thread overview]
Message-ID: <13196709.post@talk.nabble.com> (raw)
In-Reply-To: <47116DD0.7010403@cygwin.com>



Larry Hall (Cygwin) wrote:
> 
> nmehta wrote:
>> 
> 
> 
> <snip>
> 
> 
>> I can also say that CYGWIN=notntsec does fix this behavior (created
>> folders
>> are no longer shared).  I have searched for information about this
>> setting
>> but haven't yet found a good explanation.  Can you shed some light on
>> what
>> this env variable does, and what are the consequences of setting it (or
>> point me to a post/resource that can explain it?)
> 
> 
> <http://cygwin.com/cygwin-ug-net/using-cygwinenv.html>
> 
> 
>> Brian Dessent wrote:
>>> Now you're just being ridiculous.  Nowhere is the mailing list described
>>> as a users mailing list, unless somebody at Nabble has messed up.  The
>>> description on cygwin.com is quite clear that this is the right list for
>>> nearly all Cygwin related topics.  And besides, it is trivially easy to
>>> show that all the Cygwin developers follow this list closely because
>>> there are hundreds if not thousands of messages by them in the archives.
>>>
>> 
>> Lighten up.  The guy got no responses for six weeks with maybe his first
>> post to the list.  Additionally, the forum on Nabble is entitled "Cygwin
>> Users".  A simple 'No, the devs do in fact read this list' would suffice.
> 
> 
> Perhaps.  But it's not a Nabble requirement that the Cygwin web site be
> avoided.  And since Nabble really has nothing whatsoever to do with
> Cygwin,
> using it as a source of data for anything Cygwin isn't a good idea.  If
> the
> OP needed to know if he was posting to the right forum, a trip to the
> Cygwin
> site would seem to be in order.  Also, it seems it's time to once again
> note
> that this isn't a paid support service.  One isn't guaranteed a response
> in any particular time-frame or even ever.  The volunteers here answer
> questions as their time and knowledge permit.  Usually, if no one answers
> a particular thread, it's because no one has a good response, at least
> at that time.  But the problem reports are always read by everyone on this
> list, including the Cygwin developers.
> 

You make some very good points.  I mainly took exception to the tone of the
response.  It's not hard to be civil and (IMO) there's no reason to call
that particular post "ridiculous".  There were however problems with it, and
I think your response points those problems out in an educational manner.
-- 
View this message in context: http://www.nabble.com/cygwin-makes-shared-folders-on-vista-tf4360979.html#a13196709
Sent from the Cygwin Users mailing list archive at Nabble.com.


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

  reply	other threads:[~2007-10-14  7:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31 16:45 jxt
2007-10-12 19:45 ` nmehta
2007-10-12 20:08   ` jxt
2007-10-12 20:39     ` Matthew Woehlke
2007-10-12 20:53   ` Brian Dessent
2007-10-13  9:17     ` nmehta
2007-10-14  1:16       ` Larry Hall (Cygwin)
2007-10-14  7:26         ` nmehta [this message]
2007-10-14 15:32           ` Christopher Faylor
2007-10-15 14:43             ` jxt
2007-10-15 16:10               ` DePriest, Jason R.
2007-11-20 14:50       ` E.Baud
2007-11-23 12:34         ` Corinna Vinschen
2007-11-23 15:12           ` Corinna Vinschen
2007-11-27 11:22             ` E.Baud
2007-11-27 20:01               ` joekrahn
2007-11-26 20:41           ` Matthew Persico

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=13196709.post@talk.nabble.com \
    --to=nmehta@cs.caltech.edu \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).