From: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
To: kusmabite@gmail.com
Cc: Pascal Obry <pascal@obry.net>, git@vger.kernel.org
Subject: Re: [PATCH 2/2] On Cygwin support both UNIX and DOS style path-names
Date: Tue, 09 Aug 2011 18:26:33 +0100 [thread overview]
Message-ID: <4E416DC9.2080907@ramsay1.demon.co.uk> (raw)
In-Reply-To: <CABPQNSYSzsY-CQdi6iJQftsY1ufMpxkax=eQLgopVxMC6LoxfA@mail.gmail.com>
Erik Faye-Lund wrote:
> On Fri, Aug 5, 2011 at 6:10 PM, Pascal Obry <pascal@obry.net> wrote:
>> In fact Cygwin supports both, so make Git agree with this.
>> The failing case is when a file is committed in a sub-dir of the
>> repository using a log message from a file specified with a DOS
>> style path-name. To reproduce:
>>
>> $ cd src
>> $ git commit -F c:\tmp\log.txt file.c
>> fatal: could not read log file 'src/c:\tmp\log.txt': No such file \
>> or directory.
>
> Cygwin is a unix-layer on top of Windows, designed to play by the
> POSIX-rules. So why would you want to support Windows-style paths on
> Cygwin?
>
> If you want a Git that handles Windows paths, use Git for Windows...
Indeed, I have to agree. This takes the cygwin port in the wrong
direction ...
ATB,
Ramsay Jones
next prev parent reply other threads:[~2011-08-09 18:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 16:10 [PATH 0/2] On Cygwin support both UNIX and DOS style path-names Pascal Obry
2011-08-05 16:10 ` [PATCH 1/2] git-compat-util: add generic find_last_dir_sep that respects is_dir_sep Pascal Obry
2011-08-05 16:10 ` [PATCH 2/2] On Cygwin support both UNIX and DOS style path-names Pascal Obry
2011-08-05 17:29 ` Erik Faye-Lund
2011-08-05 17:35 ` Pascal Obry
2011-08-05 17:39 ` Erik Faye-Lund
2011-08-05 17:51 ` Erik Faye-Lund
2011-08-05 18:39 ` Pascal Obry
2011-08-09 17:30 ` Ramsay Jones
2011-08-09 17:26 ` Ramsay Jones [this message]
2011-08-05 17:48 ` Junio C Hamano
2011-08-05 17:58 ` Erik Faye-Lund
2011-08-06 7:01 ` Pascal Obry
2011-08-09 17:24 ` Ramsay Jones
2011-08-09 20:38 ` Pascal Obry
2011-08-11 20:35 ` Ramsay Jones
2011-08-13 17:34 ` Pascal Obry
2011-08-10 2:44 ` Vijay Lakshminarayanan
2011-08-09 19:47 ` Johannes Sixt
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=4E416DC9.2080907@ramsay1.demon.co.uk \
--to=ramsay@ramsay1.demon.co.uk \
--cc=git@vger.kernel.org \
--cc=kusmabite@gmail.com \
--cc=pascal@obry.net \
/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.