Re: [PATCH] Handle UNC paths everywhere

From: Erik Faye-Lund <kusmabite@googlemail.com>
Date: Jan 25, 2010, 17:57 UTC
Message-ID: <40aa078e1001250957h292f8b01me8f7dec4ba2b425b@mail.gmail.com>
In-Reply-To: <alpine.DEB.1.00.1001251553150.8733@intel-tinevez-2-302>

On Mon, Jan 25, 2010 at 6:34 PM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

Show 14 quoted lines

> Hi,
>
> On Mon, 25 Jan 2010, Robin Rosenberg wrote:
>
>> >From 37a74ccd395d91e5662665ca49d7f4ec49811de0 Mon Sep 17 00:00:00 2001
>> From: Robin Rosenberg <robin.rosenberg@dewire.com>
>> Date: Mon, 25 Jan 2010 01:41:03 +0100
>> Subject: [PATCH] Handle UNC paths everywhere
>>
>> In Windows paths beginning with // are knows as UNC paths. They are
>> absolute paths, usually referring to a shared resource on a server.
>
> And even a simple "cd" with them does not work.
>

But it does, at least for me - both in bash and cmd.exe. I just need to log on to the server first, unless it's a public share.

-- 
Erik "kusma" Faye-Lund