Re: [PATCH] HACKING: More language clean-up
From: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2004-10-12 16:05:45 CEST
Michael W Thelen wrote:
>> Include missing trailing slash on http://apr.apache.org (slashes are used
OK, though that's not as important as including the slash when the URL ends in a subdirectory. But since you're making other changes to this file you might as well fix this.
>> Clarify that the key for secure programming is developer understanding,
I don't see that the meaning was unclear before. Not that your replacement is worse, but I don't see the need to change it. Surely it's obvious that if a developer has already been educated sufficiently in the subject, then this shouldn't be read as implying that he still needs more. This is aimed at new readers of the HACKING file, and it is reasonable to assume that most of them are not "educated" to the desired degree in this subject. Or maybe you don't like the word "education" because it implies a formal, structured activity, whereas any means of learning is of course acceptable.
I won't stop you changing it if you're sure that you are improving it, but I'm not sure.
>> Removed 'staked' from 'staked ownership', as it's neither formal nor
I don't understand your objection. What isn't formal or complete? The staking of ownership? This is talking about staking of ownership as a possible impression on a new reader, not as something that really existed. Note that "appears to have staked" is the verb phrase, and "ownership" the noun; were you reading it as "appears to have" and "staked ownership"? The wordings "appears to have staked ownership on the file" and "appears to have ownership of the file" mean effectively the same to me, but with the former (original) case additionally conveying the desired impression of "staking" being the writing of the "owner's" name in the file with intent to claim the file as his/her own.
So I disagree with this change.
>> Additional linguistic tweaks.
Yes. ("a" -> "an"; "can into" -> "can go into".)
> Thanks for the patch. I've filed it as issue #2097:
This is an archived mail posted to the Subversion Dev mailing list.