It's a mistake. We'll get it fixed! Alan
On 27 January 2013 01:49, Bang Jun-young <junyo...@mogua.com> wrote: > I have the same problem on Windows. Two of those files have invisible > trailing spaces in their names. I'm curious how they could have been > committed in the first place. A bug in Git? > > On Sat, Jan 26, 2013 at 3:53 AM, sebastian > <sebast...@palladiumconsulting.com> wrote: >> I cloned the mono/mono repo to a Windows machine, and no matter what I do, >> my git status reports thusly: >> >> $ git status >> # On branch master >> # Changes not staged for commit: >> # (use "git add <file>..." to update what will be committed) >> # (use "git checkout -- <file>..." to discard changes in working >> directory) >> # >> # modified: mcs/class/monodoc/monodoc.dll.sources >> # modified: mcs/class/monodoc/monodoc_test.dll.sources >> # >> no changes added to commit (use "git add" and/or "git commit -a") >> >> Signs suggest this is due to files which differ only by case, which can make >> Windows & OS X unhappy. I can commit the bogus change locally, but it >> reappears when moving to a tag. >> >> _______________________________________________ >> Mono-devel-list mailing list >> Mono-devel-list@lists.ximian.com >> http://lists.ximian.com/mailman/listinfo/mono-devel-list >> > _______________________________________________ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list