Re: [boost] Can SVN Check for too long and CamelCase file names?

From: Paul A Bristow (pbristow_at_[hidden])
Date: 2007-08-29 11:53:12

>-----Original Message-----
>From: boost-bounces_at_[hidden] 
>[mailto:boost-bounces_at_[hidden]] On Behalf Of Doug Gregor
>Sent: 29 August 2007 16:46
>To: boost_at_[hidden]
>Subject: Re: [boost] Can SVN Check for too long and CamelCase 
>file names?
>
>
>On Aug 28, 2007, at 5:15 AM, Paul A Bristow wrote:
>
>> I have recently had my wrist slapped by John Maddock, not once, but  
>> twice :-((
>>
>> My offences were committing both
>>
>> Too long filenames, and
>>
>> CamelCaseFileNames.
>>
>> Are either of these crimes that could be prevented by SVN pre- 
>> commit rules?
>
>The Subversion repository now checks that there are no problems with  
>case-insensitive file systems (based on the case-insensitive.py pre- 
>commit hook). So committing "Jamfile" is file, but a commit of  
>"JamFile" when there is already a "Jamfile" will be rejected.
>
>We also now reject commits containing filenames with > 31 characters.

Thanks for saving my wrist from further chastisement by John ;-)

Paul

PS We still need to resolve WHY the original submission rules said "No uppercase". 

"These requirements ensure file and directory names are relatively portable"

 Are those requirements still valid on some platform?

And we need to agree to change the requirements if we can agree they are no longer needed.

---
Paul A Bristow
Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB
[phone] & SMS, Mobile [phone] & SMS
pbristow_at_[hidden]