All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Levedahl <mlevedahl@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/5] "best effort" checkout
Date: Thu, 29 May 2008 21:09:44 -0400	[thread overview]
Message-ID: <483F53D8.1020201@gmail.com> (raw)
In-Reply-To: <7vabi8ocju.fsf@gitster.siamese.dyndns.org>

Junio C Hamano wrote:
> I hope you did not use 6/5.  My understanding is that your platform
> natively supports it without that compatibility layer ;-)
>   
That is a very polite way to express things, and no I did not apply that 
patch.
>
> I expected to see "deleted" here.  I guess lstat("anything/nul") says "it
> exists" everywhere, and that probably is why you are getting EEXIST.
>
>   
Indeed:

git>ls nul
nul
git>ls nul*
ls: cannot access nul*: No such file or directory

So, any test for existence of <path>NUL will pass, but NUL never appears 
in a directory listing. The same is true of the other special filenames 
under Windows (aux, ...).

Mark

      reply	other threads:[~2008-05-30  1:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-29  0:17 [PATCH 0/5] "best effort" checkout Junio C Hamano
2008-05-29  0:17 ` [PATCH 1/5] "git checkout -- paths..." should error out when paths cannot be written Junio C Hamano
2008-05-29  0:17   ` [PATCH 2/5] checkout: make reset_clean_to_new() not die by itself Junio C Hamano
2008-05-29  0:17     ` [PATCH 3/5] checkout: consolidate reset_{to_new,clean_to_new|() Junio C Hamano
2008-05-29  0:17       ` [PATCH 4/5] unpack_trees(): allow callers to differentiate worktree errors from merge errors Junio C Hamano
2008-05-29  0:17         ` [PATCH 5/5] checkout: "best effort" checkout Junio C Hamano
2008-05-29  0:17           ` [PATCH 6/5] NUL hack to create_file() Junio C Hamano
2008-05-29  6:33             ` Johannes Sixt
2008-05-29  7:05               ` Marius Storm-Olsen
2008-05-29  7:23                 ` Johannes Sixt
2008-05-29 17:19                 ` Daniel Barkalow
2008-05-29 17:51                   ` Brian Dessent
2008-05-29 18:35                     ` Daniel Barkalow
2008-05-29 12:39               ` Johannes Schindelin
2008-05-29 15:55             ` Daniel Barkalow
2008-05-29 18:26               ` Junio C Hamano
2008-05-29 17:44             ` Alex Riesen
2008-05-29 23:24 ` [PATCH 0/5] "best effort" checkout Mark Levedahl
2008-05-30  0:33   ` Junio C Hamano
2008-05-30  1:09     ` Mark Levedahl [this message]

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=483F53D8.1020201@gmail.com \
    --to=mlevedahl@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 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.