Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Fri, 27 Jul 2001 12:12:49 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: per-process mounts (Was: directory hard links) Message-ID: <20010727121249.D3518@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <85256A96.0057F738.00@nyc-ntgw-n01.ny.jpmorgan.com> <3B6192DC.EB31BDC8@cportcorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3B6192DC.EB31BDC8@cportcorp.com>; from peter.buckley@cportcorp.com on Fri, Jul 27, 2001 at 12:12:12PM -0400 On Fri, Jul 27, 2001 at 12:12:12PM -0400, Peter Buckley wrote: >An RFE? I don't think cygwin really operates with that business model. >If you would like cygwin to have a feature, AFAIK SOP is that you write >a patch or create a package and become the maintainer. You also would >need approval for the patch/package. Cygwin is a maintained by a >community effort. Bingo. Since I'm not interested in doing this and (I assume) Corinna is not interested in doing this, that leaves a couple of other Cygwin developers who are familiar with the path handling code in cygwin. If you can get them interested, then maybe they'll tackle this. Otherwise, you'll need to provide a patch. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/