On 03/07/2014 11:29, Warner Losh wrote: > On Mar 7, 2014, at 10:22 AM, Ian Lepore <i...@freebsd.org> wrote: > >> On Fri, 2014-03-07 at 10:19 -0700, Warner Losh wrote: >>> On Mar 7, 2014, at 9:47 AM, Eitan Adler <li...@eitanadler.com> wrote: >>> >>>> On 7 March 2014 11:41, Rui Paulo <rpa...@freebsd.org> wrote: >>>>> On 6 Mar 2014, at 23:30, David Xu <davi...@freebsd.org> wrote: >>>>>> it seems filename ended with a dot is illegal on Windows, if someone >>>>>> wants to check out freebsd source code on Windows, it will be a problem. >>>>> Is this something we want to support? >>>> Yes. >>>> >>>>> NetBSD made some invasive changes on their source tree to be able to >>>>> support case-insensitive filesystems (like renaming 'cvs' to 'xcvs' to >>>>> avoid clashing with the 'CVS' metadata directory), but they support >>>>> building NetBSD on many different platforms. >>>> Has anyone enumerated the problematic files for FreeBSD ? >>> Last time I looked there were only a handful. I’ll conduct a census and get >>> a concrete enumeration of the problem… >> Last time I noticed (early last year) there were 3 files ending in a dot >> and no case conflicts. Mercurial now finds just the one file ending in >> a dot and no case conflicts (doing "hg init;hg add -q" at /usr/src). > Confirmed via regex, almost… Now there’s only one ending in dot: > > ./tools/test/sort/bigtest/q-1.024.003.
I confirmed, using Git, that this is the only problematic file when checking out head on Windows. On stable/9, lib/libc/gen/aux.c is the only problem. If someone is interested, r239193 could be MFC'd. On stable/8, some files under share/doc/psd/15.yacc are the only problem. r210167 could be MFC'd. Eric _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
