git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: "Johannes Sixt" <j6t@kdbg.org>,
	"Junio C Hamano" <gitster@pobox.com>,
	git@vger.kernel.org, "Michael Blume" <blume.mike@gmail.com>,
	"Torsten Bögershausen" <tboegi@web.de>
Subject: Re: [PATCH] t0060: loosen overly strict expectations
Date: Fri, 15 Jan 2016 07:34:21 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1601150730440.2964@virtualbox> (raw)
In-Reply-To: <5698415E.7070907@ramsayjones.plus.com>

Hi Ramsay,

On Fri, 15 Jan 2016, Ramsay Jones wrote:

> On 14/01/16 22:14, Johannes Sixt wrote:
> > Am 14.01.2016 um 19:13 schrieb Ramsay Jones:
> >> Correct me if I'm wrong (quite possible), but _each_ drive has a
> >> current working directory associated with it in win32, so it's a bit
> >> difficult to use drive designators with a relative path (eg.
> >> C:usr/lib).
> > 
> > As far as it matters for Git, such a path is still an absolute path,
> > because it is not anchored at $(pwd).
> 
> [...] seems to contradict what you say above.
> 
> What am I missing?

The missing bit is: while C:usr/lib is *not* anchored on $(pwd), it is
*still* not an absolute path because it is anchored on the current
directory of the C: drive (the entire idea that some drive state can
change the meaning of "C:usr/lib" makes it a non-absolute one).

Since this concept -- a path that is neither relative to $(pwd) nor
absolute -- does not exist on Linux, I do not think that Git for Windows
handles this case well at all.

Ciao,
Dscho

  reply	other threads:[~2016-01-15  6:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14  6:48 [PATCH] t0060: loosen overly strict expectations Johannes Schindelin
2016-01-14 17:33 ` Junio C Hamano
2016-01-14 18:13   ` Ramsay Jones
2016-01-14 22:14     ` Johannes Sixt
2016-01-15  0:46       ` Ramsay Jones
2016-01-15  6:34         ` Johannes Schindelin [this message]
2016-01-15 14:53           ` Ramsay Jones
2016-01-15  6:54         ` Johannes Sixt
2016-01-15 14:55           ` Ramsay Jones
2016-01-14 18:52 ` Eric Sunshine
2016-01-15  6:35   ` Johannes Schindelin
2016-01-15 17:26     ` Junio C Hamano
2016-01-19  9:40       ` Johannes Schindelin

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=alpine.DEB.2.20.1601150730440.2964@virtualbox \
    --to=johannes.schindelin@gmx.de \
    --cc=blume.mike@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j6t@kdbg.org \
    --cc=ramsay@ramsayjones.plus.com \
    --cc=tboegi@web.de \
    /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).