From: Sverre Rabbelier <srabbelier@gmail.com>
To: Robin Rosenberg <robin.rosenberg@dewire.com>
Cc: git@vger.kernel.org, Johannes Sixt <j6t@kdbg.org>,
Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH] Handle UNC paths everywhere
Date: Mon, 25 Jan 2010 10:36:59 +0100 [thread overview]
Message-ID: <fabb9a1e1001250136n2fb0043av7348db9177f4d096@mail.gmail.com> (raw)
In-Reply-To: <201001250155.47664.robin.rosenberg@dewire.com>
Heya,
On Mon, Jan 25, 2010 at 01:55, Robin Rosenberg
<robin.rosenberg@dewire.com> wrote:
> In Windows paths beginning with // are knows as UNC paths. They are
> absolute paths, usually referring to a shared resource on a server.
Cute, but will it actually work? I've tried to use them // paths on
windows before with MSysGit, and it's never worked, probably due to
the same reason why it doesn't work in the cmd prompt (whatever reason
that may be).
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2010-01-25 9:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 0:55 [PATCH] Handle UNC paths everywhere Robin Rosenberg
2010-01-25 9:36 ` Sverre Rabbelier [this message]
2010-01-25 9:58 ` Robin Rosenberg
2010-01-25 10:11 ` Erik Faye-Lund
2010-01-25 10:22 ` Sverre Rabbelier
2010-01-25 11:01 ` Robin Rosenberg
2010-01-25 11:06 ` Sverre Rabbelier
2010-01-25 11:17 ` Erik Faye-Lund
2010-01-25 17:34 ` Johannes Schindelin
2010-01-25 17:57 ` Erik Faye-Lund
2010-01-25 18:19 ` Johannes Schindelin
2010-01-25 19:45 ` Erik Faye-Lund
2010-01-25 19:37 ` Robin Rosenberg
2010-01-25 19:48 ` Erik Faye-Lund
2010-01-25 20:15 ` Robin Rosenberg
2010-01-25 19:45 ` Robin Rosenberg
2010-01-26 10:59 ` Johannes Schindelin
2010-01-25 20:04 ` Robin Rosenberg
2010-01-26 11:01 ` Johannes Schindelin
2010-01-25 20:07 ` Johannes Sixt
2010-01-25 21:42 ` Robin Rosenberg
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=fabb9a1e1001250136n2fb0043av7348db9177f4d096@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=robin.rosenberg@dewire.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 NNTP newsgroup(s).