"C. Michael Pilato" <cmpil...@collab.net> writes: > On 02/21/2011 09:30 PM, Noorul Islam K M wrote: > >> Branko Čibej <br...@e-reka.si> writes: >> >>> On 22.02.2011 02:50, Noorul Islam K M wrote: >>> >>>> danie...@apache.org writes: >>>> >>>>> Author: danielsh >>>>> Date: Mon Feb 21 18:14:02 2011 >>>>> New Revision: 1073102 >>>>> >>>>> URL: http://svn.apache.org/viewvc?rev=1073102&view=rev >>>>> Log: >>>>> * subversion/include/private/svn_debug.h >>>>> (SVN_DBG): Merge docstring with the documentation comment elsefile. >>>>> >>>> Is this typo? ^^^^^^^^ >>> >>> Nah, it's just creative language. "Elsewhere" sounds so plain and >>> boring. Who cares that the result is total nonsense and likely to be >>> misunderstood by 99% of all readers? :) >>> >> >> But why do we have to use that? Is it not possible to use proper English >> word and still be creative? > > There's a history of joviality in the Subversion project that many of us > would like to preserve indefinitely. Unfortunately, that often comes at a > cost similar to any other "inside joke", especially where natural language > barriers exist. I confess that I'm not really sure where to strike the > proper balance here, but I'm confident that Confusion isn't one of our core > project goals. Would you like someone to tweak the message not to use the > fictional term "elsefile"?
When I read the commit log, I did not understand what that word "elsefile" meant. Do you think new members should get confused by something like this? Do you think the following makes sense? * subversion/include/private/svn_debug.h (SVN_DBG): Merge docstring with the documentation comment. Thanks and Regards Noorul