Re: Commit cce8d6fdb introduces file t/t5100/nul, git tree is now incompatible with Cygwin (and probably Windows)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Mon, 26 May 2008, Mark Levedahl wrote:

> Beginning with the referenced commit, the git project cannot be checked 
> out on Cygwin (and I assume cannot be checked out on Windows using 
> msysgit, though I have not verified this) as this commit introduces the 
> file "t/5100/nul." On Windows, the file name "nul" is reserved, 
> regardless of path, and cannot be created or deleted. It serves 
> essentially the same function as /dev/null.

Even when referencing the full (or a relative) path?  That's bad!

> As a for instance of the troubles:
> 
> git>git checkout -f origin/master
> Previous HEAD position was a2f5be5... Merge branch
> 'jk/maint-send-email-compose' into maint
> error: git-checkout-index: unable to create file t/t5100/nul (File exists)
> 
> As this commit is part of the published master branch, I am not sure the 
> correct resolution: leaving this commit in place means that any commit 
> between it and a commit fixing this will always cause an error on Cygwin 
> / Windows. Of course, it *is* on the published master branch.

That's the case for all regressions: we do not rewrite history for them.

As for the resolution, could you quickly try the 'my-next' branch of 
git://repo.or.cz/git/dscho.git?

If that works, I'll send a proper patch to Junio.

Ciao,
Dscho

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux