Re: Strange git issue with a particular repo
On 2018-08-05 08:01, Ken Brown wrote:
> On 8/5/2018 5:31 AM, James Darnley wrote:
>> You can clone it successfully on Windows if you enable case sensitivity,
>> which is probably not recommended but possible with a registry change.
> I wouldn't say this is not recommended. It's documented in the Cygwin User's
> Guide:
> https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive
> I've been setting up my Cygwin systems to be case sensitive for years with no
> problems.
Cygwin could now support doing so in its own directories on current Win
releases:
https://blogs.msdn.microsoft.com/commandline/2018/02/28/per-directory-case-sensitivity-and-wsl/
with currently documented interfaces:
fsutil file {query|set}CaseSensitiveInfo [enable|disable]
although this "flag" does not appear to be an inheritable attribute, so has to
be manually applied recursively to subdirs.
It also appears to be supported by DrvFS mount option case=off|dir|force, where
the first two alternatives honour the flag, the second and third adds it to
directories created on those mounts, and the third ignores the flag treating all
names as case sensitive.
This might be useful as a Windows git option, but not under Cygwin just now,
unless someone added support for an option supporting it on earlier releases
also.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Strange git issue with a particular repo
Greetings, Ken Brown! > On 8/5/2018 5:31 AM, James Darnley wrote: >> You can clone it successfully on Windows if you enable case sensitivity, >> which is probably not recommended but possible with a registry change. > I wouldn't say this is not recommended. It's documented in the Cygwin > User's Guide: > https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive > I've been setting up my Cygwin systems to be case sensitive for years > with no problems. If you want case sensitivity, it's best to configure it on a per-volume basis. Mindlessly turning it on in registry is going to cause interoperability issues with other systems. -- With best regards, Andrey Repin Sunday, August 5, 2018 18:15:56 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Strange git issue with a particular repo
On 8/5/2018 5:31 AM, James Darnley wrote: You can clone it successfully on Windows if you enable case sensitivity, which is probably not recommended but possible with a registry change. I wouldn't say this is not recommended. It's documented in the Cygwin User's Guide: https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive I've been setting up my Cygwin systems to be case sensitive for years with no problems. Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Strange git issue with a particular repo
James Darnley wrote: > I don't think it is a rename in the history. I think it is because both > regdir/T.sub and regdir/t.sub exist in the dame directory, for example. > You can clone it successfully on Windows if you enable case sensitivity, > which is probably not recommended but possible with a registry change. That's exactly it! There are 6 such files, and it's those that show the problem. I guess I will look into renaming some of the files to avoid such conflicts. Thanks very much for the help! Arnold -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Strange git issue with a particular repo
On 2018-08-05 10:21, arn...@skeeve.com wrote: > Hi. > > john doe wrote: > >> Linux is case sensitive and Windows is case preserving. >> That is probably the issue here, did the case of the files has been >> changed (rename 100%)? >> >> https://docs.microsoft.com/en-us/vsts/repos/git/case-sensitivity?view=vsts >> >> In other words, on "Cygwin" git can not handle files defering only by >> the case. > > It's possible, but I don't think so. Is there a straightforward way to > tell? Although I've been using git for a while, I'm not a major league > guru. I don't think it is a rename in the history. I think it is because both regdir/T.sub and regdir/t.sub exist in the dame directory, for example. You can clone it successfully on Windows if you enable case sensitivity, which is probably not recommended but possible with a registry change. signature.asc Description: OpenPGP digital signature
Re: Strange git issue with a particular repo
Hi. john doe wrote: > Linux is case sensitive and Windows is case preserving. > That is probably the issue here, did the case of the files has been > changed (rename 100%)? > > https://docs.microsoft.com/en-us/vsts/repos/git/case-sensitivity?view=vsts > > In other words, on "Cygwin" git can not handle files defering only by > the case. It's possible, but I don't think so. Is there a straightforward way to tell? Although I've been using git for a while, I'm not a major league guru. Thanks! Arnold -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Strange git issue with a particular repo
On 8/5/2018 9:12 AM, arn...@skeeve.com wrote: Hi All. Please cc me on responses, as I don't subscribe to the list. I'm using a 64 bit install on Windows 10. I just now did an update and it did not help. The problem is with a particular repo only. (Or at least, I only see it with this particular repo.) On Linux, do: git clone git://github.com/arnoldrobbins/bwk-awk cd bwk-awk git status You should see something like this: $ git clone git://github.com/arnoldrobbins/bwk-awk Initialized empty Git repository in /u/arnold/bwk-awk/.git/ remote: Counting objects: 463, done. remote: Compressing objects: 100% (16/16), done. remote: Total 463 (delta 1), reused 6 (delta 1), pack-reused 444 Receiving objects: 100% (463/463), 5.06 MiB | 1.77 MiB/s, done. Resolving deltas: 100% (79/79), done. $ cd bwk-awk $ git status # On branch master nothing to commit (working directory clean) On Cygwin, something strange happens instead: $ git clone git://github.com/arnoldrobbins/bwk-awk Cloning into 'bwk-awk'... remote: Counting objects: 463, done. remote: Compressing objects: 100% (16/16), done. remote: Total 463 (delta 1), reused 6 (delta 1), pack-reused 444 Receiving objects: 100% (463/463), 5.06 MiB | 2.33 MiB/s, done. Resolving deltas: 100% (79/79), done. $ cd bwk-awk $ git status On branch master Your branch is up to date with 'origin/master'. Changes not staged for commit: (use "git add ..." to update what will be committed) (use "git checkout -- ..." to discard changes in working directory) modified: regdir/Compare.T modified: regdir/T.delete modified: regdir/T.getline modified: regdir/T.redir modified: regdir/T.split modified: regdir/T.sub no changes added to commit (use "git add" and/or "git commit -a") The "modified" files are from an earlier commit. Doing git reset --hard has no effect. On cygwin: $ git --version git version 2.17.0 On Linux: $ git --version git version 1.7.1 But it also works OK on a Linux system with git 2.17.1. Any help would be appreciated. I hope that you can reproduce it. Linux is case sensitive and Windows is case preserving. That is probably the issue here, did the case of the files has been changed (rename 100%)? https://docs.microsoft.com/en-us/vsts/repos/git/case-sensitivity?view=vsts In other words, on "Cygwin" git can not handle files defering only by the case. -- John Doe -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Strange git issue with a particular repo
Hi All. Please cc me on responses, as I don't subscribe to the list. I'm using a 64 bit install on Windows 10. I just now did an update and it did not help. The problem is with a particular repo only. (Or at least, I only see it with this particular repo.) On Linux, do: git clone git://github.com/arnoldrobbins/bwk-awk cd bwk-awk git status You should see something like this: $ git clone git://github.com/arnoldrobbins/bwk-awk Initialized empty Git repository in /u/arnold/bwk-awk/.git/ remote: Counting objects: 463, done. remote: Compressing objects: 100% (16/16), done. remote: Total 463 (delta 1), reused 6 (delta 1), pack-reused 444 Receiving objects: 100% (463/463), 5.06 MiB | 1.77 MiB/s, done. Resolving deltas: 100% (79/79), done. $ cd bwk-awk $ git status # On branch master nothing to commit (working directory clean) On Cygwin, something strange happens instead: $ git clone git://github.com/arnoldrobbins/bwk-awk Cloning into 'bwk-awk'... remote: Counting objects: 463, done. remote: Compressing objects: 100% (16/16), done. remote: Total 463 (delta 1), reused 6 (delta 1), pack-reused 444 Receiving objects: 100% (463/463), 5.06 MiB | 2.33 MiB/s, done. Resolving deltas: 100% (79/79), done. $ cd bwk-awk $ git status On branch master Your branch is up to date with 'origin/master'. Changes not staged for commit: (use "git add ..." to update what will be committed) (use "git checkout -- ..." to discard changes in working directory) modified: regdir/Compare.T modified: regdir/T.delete modified: regdir/T.getline modified: regdir/T.redir modified: regdir/T.split modified: regdir/T.sub no changes added to commit (use "git add" and/or "git commit -a") The "modified" files are from an earlier commit. Doing git reset --hard has no effect. On cygwin: $ git --version git version 2.17.0 On Linux: $ git --version git version 1.7.1 But it also works OK on a Linux system with git 2.17.1. Any help would be appreciated. I hope that you can reproduce it. Thanks! Arnold -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
