From: Ramsay Jones <ramsay@ramsayjones•plus.com>
To: Johannes Sixt <j6t@kdbg•org>
Cc: "Junio C Hamano" <gitster@pobox•com>,
"Johannes Schindelin" <johannes.schindelin@gmx•de>,
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 14:55:16 +0000 [thread overview]
Message-ID: <56990854.5080005@ramsayjones.plus.com> (raw)
In-Reply-To: <569897B7.4040302@kdbg.org>
On 15/01/16 06:54, Johannes Sixt wrote:
> Am 15.01.2016 um 01:46 schrieb Ramsay Jones:
>>
>>
>> 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).
>>
>> I have been using cygwin on windows since beta-18 (about 1995), in order
>> to avoid most of the horrors of the windows command line, so I'm a little
>> rusty. ;-)
>>
>> You know windows _much_ better than me, so could you please educate me
>> on this point. I tried this (on windows 8.1):
>
>> C:\cygwin64\home\ramsay\junk>dir C:sub-1
>> dir C:sub-1
>> Volume in drive C is TI31255200A
>> Volume Serial Number is 0024-4AC0
>>
>> Directory of C:\cygwin64\home\ramsay\junk\sub-1
>> [...]
>>
>> ... which seems to contradict what you say above.
>
> This example is not super-illuminating. You must cd to a directory on a different drive, say D:\foo, then call dir C:sub-1. The result will be the directory listing from somewhere deep inside the C: hierarchy, not from inside D:\foo.
>
>>
>> What am I missing?
>
> Git assumes, given a path in $path that is declared to be relative, that "$path" and "$(pwd)/$path" denote the same thing.
>
> But that does not work when path="C:sub-1". Yeah, "C:sub-1" is relative to something, but *in general* that something is not $(pwd).
I obviously didn't express myself very well, but your answer seems to
be in violent agreement with what I wanted to say! ;-)
ATB,
Ramsay Jones
next prev parent reply other threads:[~2016-01-15 14:55 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
2016-01-15 14:53 ` Ramsay Jones
2016-01-15 6:54 ` Johannes Sixt
2016-01-15 14:55 ` Ramsay Jones [this message]
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=56990854.5080005@ramsayjones.plus.com \
--to=ramsay@ramsayjones$(echo .)plus.com \
--cc=blume.mike@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=j6t@kdbg$(echo .)org \
--cc=johannes.schindelin@gmx$(echo .)de \
--cc=tboegi@web$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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