X-Spam-Check-By: sourceware.org
Date: Fri, 13 Oct 2006 12:26:21 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] Updated: vim-7.0.122-1
Message-ID: <20061013102621.GJ8323@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <egjc38$teg$1 AT sea DOT gmane DOT org> <20061012065523 DOT GP13105 AT calimero DOT vinschen DOT de> <20061012111836 DOT GA29649 AT trixie DOT casa DOT cgf DOT cx> <20061012115416 DOT GB8323 AT calimero DOT vinschen DOT de> <51442 DOT 84 DOT 246 DOT 168 DOT 11 DOT 1160654571 DOT squirrel AT mail DOT morrison DOT mine DOT nu> <Pine DOT GSO DOT 4 DOT 63 DOT 0610120924170 DOT 28291 AT access1 DOT cims DOT nyu DOT edu> <40944 DOT 84 DOT 246 DOT 168 DOT 11 DOT 1160663798 DOT squirrel AT mail DOT morrison DOT mine DOT nu> <20061012144859 DOT GF8323 AT calimero DOT vinschen DOT de> <20061012145226 DOT GG8323 AT calimero DOT vinschen DOT de> <Pine DOT GSO DOT 4 DOT 63 DOT 0610122205460 DOT 2556 AT access1 DOT cims DOT nyu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.63.0610122205460.2556@access1.cims.nyu.edu>
User-Agent: Mutt/1.4.2i
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Oct 12 22:08, Igor Peshansky wrote:
> On Thu, 12 Oct 2006, Corinna Vinschen wrote:
> > > So it looks like using mixed paths (cygpath -m) would be an easy way
> > > out of this for now.
> >
> > Naah, scratch that.  Creating a mount point for $SYSTEMROOT seems the
> > better solution.
> 
> I'll go with mixed case.  The mount point for $SYSTEMROOT will either have
> to be explicitly created, or it will need to be built into cygwin1.dll.
> In the former case, it's more hassle for the user; [...]

I think the idea here was that the base-file package would create the
mount point, if /WINDOWS doesn't exist already.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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