From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: gitzilla@gmail.com, Steffen Prohaska <prohaska@zib.de>,
Pascal Obry <pascal@obry.net>,
git@vger.kernel.org
Subject: Re: [PATCH] Makefile: fix misdetection of relative pathnames
Date: Thu, 05 Feb 2009 09:19:31 -0800 [thread overview]
Message-ID: <7v1vucg5ss.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <498ADB1B.7030300@viscovery.net> (Johannes Sixt's message of "Thu, 05 Feb 2009 13:27:07 +0100")
Johannes Sixt <j.sixt@viscovery.net> writes:
> That said, I don't think it's worth to cater for this use-case, precisely
> because we want to *avoid* absolute paths on Windows anyway, and apply the
> change that you proposed here.
>
> [*] The reason it does not work is that we cannot use MSYS-style absolute
> paths /c/Foo/Bar because the paths will be interpreted by git, which does
> not understand them; the user must specify drive-letter absolute paths
> c:/Foo/Bar, but the check does not catch them.
Hmm, not c:\Program Files\Git?
In any case, thanks for an Ack. It clears one remaining issue for -rc0
(and there are certainly others I have forgot).
next prev parent reply other threads:[~2009-02-05 17:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 18:24 026fa0d5ad Breaks installs with absolue $(gitexecdir) and $(template_dir) variables using older GNU makes A Large Angry SCM
2009-02-05 7:04 ` Junio C Hamano
2009-02-05 7:13 ` Steffen Prohaska
2009-02-05 7:35 ` Junio C Hamano
2009-02-05 7:38 ` Pascal Obry
2009-02-05 7:53 ` Junio C Hamano
2009-02-05 7:57 ` Pascal Obry
2009-02-05 8:01 ` Junio C Hamano
2009-02-05 7:44 ` Junio C Hamano
2009-02-05 8:18 ` [PATCH] Makefile: fix misdetection of relative pathnames Junio C Hamano
2009-02-05 12:27 ` Johannes Sixt
2009-02-05 17:19 ` Junio C Hamano [this message]
2009-02-05 22:16 ` A Large Angry SCM
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=7v1vucg5ss.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitzilla@gmail.com \
--cc=j.sixt@viscovery.net \
--cc=pascal@obry.net \
--cc=prohaska@zib.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.