- From: Mary Brady <mbrady@nist.gov>
- Date: Wed, 22 Aug 2001 08:48:16 -0400
- To: "Curt Arnold" <carnold@houston.rr.com>, <www-dom-ts@w3.org>
Yes, I think this may be a result of running samba in a unix-w2000 environment where file systems are shared. I think the default may be lowercase when going between systems... --Mary ----- Original Message ----- From: "Curt Arnold" <carnold@houston.rr.com> To: <www-dom-ts@w3.org> Sent: Tuesday, August 21, 2001 2:16 PM Subject: Re: Some feedback on the DOM level 1 core tests > Joseph Kesselman wrote: > > > (Of course, readability of those names is rather marginal anyway. I > > presume > > > people have already considered camelCasedNames...?) > > > > Unfortunately, I had to lose the camel case names that were in the test > > definitions since the .ZIP file names were all lower case. I've only had > > nightmares trying the change the capitalization of filenames once they > were > > in CVS (note the screwy capitalization in the source for domunit). > > Actually wouldn't we prefer UpperCasedNames instead of camelCasesNames? > > If a CVS god can repair the file names (I can produce a list of the > original intended names from the NIST zip file), I could readily get the > content back in synch with the new file names. However, from my limited > experience with CVS, trying to work with files that only differ in case is > prone to catastrophy. I think the only approach that would work is renaming > the repository files. > > I would recommend that Mary try to preserve the capitalization on their DOM > L2 submission or we can fix it up before committing it to the CVS. I only > realized the problem once I got to the java compile process which occurred > after the files were in the CVS and a substantial amount of changes to the > test sources had occurred. > >
Received on Wednesday, 22 August 2001 08:49:40 UTC