Date: Thu, 14 Mar 2019 21:29:02 -0700 From: Enji Cooper <yaneurabeya@gmail.com> To: Ed Maste <emaste@freebsd.org> Cc: "Rodney W. Grimes" <rgrimes@freebsd.org>, src-committers <src-committers@freebsd.org>, svn-src-all <svn-src-all@freebsd.org>, svn-src-head <svn-src-head@freebsd.org> Subject: Re: svn commit: r345138 - head/share/man/man9 Message-ID: <75FBF3E0-A236-48FE-8AB9-3AFBB039CE59@gmail.com> In-Reply-To: <CAPyFy2B09hOx=tSNOMSCyhW9SdP_5ySfOuTFQZvZutfhgTi2bg@mail.gmail.com> References: <CAPyFy2CEbKMNVUJ6_mthfq3QL6tq5V0jjoZ01eX82-2kwqLFkQ@mail.gmail.com> <201903150210.x2F2ABwZ027877@gndrsh.dnsmgr.net> <CAPyFy2B09hOx=tSNOMSCyhW9SdP_5ySfOuTFQZvZutfhgTi2bg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Before all of the uuencoded files get decoded in the tree.. are we sure that non-uuencoded binary files will be proper identified if the mime type is nonexistent in svn? What about other VCSes like hg? I’m asking, because not all downstream vendors have the newest versions of svn, once upon a time, may have mashed mime types, etc, which may have interesting downstream effects if the binary type isn’t detected properly. Thank you, -Enji
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?75FBF3E0-A236-48FE-8AB9-3AFBB039CE59>