"Answered where you did" ... huh? What do you mean? Where, what?
Please speak explicitly. On Jul 29, 2011 9:56 PM, "Greg Stein" <[email protected]> wrote: > Geezus. You are continuing to be obtuse. I have *no* idea what you're > talking about. > On Jul 29, 2011 9:21 AM, "Dennis E. Hamilton" <[email protected]> > wrote: >> Greg, your short reply was completely sufficient. >> >> It was all I needed and it answered the question that I asked. >> >> It was a little odd that you answered it where you did, but I got the > answer. >> >> The question was about a practice that I observed you following, not about > ALv2 nor the difference between work contributed to Apache and when > contributing work to a non-Apache project under an ALv2 license. The gist of > my note is about the apparent social dynamics of answers to unasked > questions. I've been noticing how often that happens on other dev lists I > follow and I was amused that it happened here with a question I asked. >> >> - Dennis >> >> -----Original Message----- >> From: Greg Stein [mailto:[email protected]] >> Sent: Friday, July 29, 2011 02:36 >> To: [email protected] >> Subject: RE: Q: Notices in Code - Answered and Thanks Y'All >> >> It seems there is some kind of subtext here, but it is so obtuse that I > have >> no idea what is going on. >> >> So: was my short reply useful, or not? >> >> And note that my reply was also given as an augment to Rob's link to > source >> header application. >> >> Dennis: be clear; *what* are you trying to say? I cannot read *any* > takeaway >> from below. >> >> -g >> On Jul 28, 2011 7:44 PM, "Dennis E. Hamilton" <[email protected]> >> wrote: >>> There's a story, perhaps apocryphal (i.e., like the bicycle shed story), >> about Tom Watson approaching a Sr.VP for Human Resources in a hallway and >> asking how college students get summer jobs at IBM. The Sr.VP said he'd > get >> back to him. >>> >>> I will say no more. You might imagine how this went South when the only >> thing Watson wanted to know was to what to tell a neighbor whose son > wanted >> to apply for one of those jobs. The more experience you have in corporate >> life (and on some developer lists), you can imagine where this might have >> ended up instead. (Serious analysis and study, crash project, charts, >> slides, big conference room presentation, etc.) >>> >>> However, Greg answered my question in his first reply on this thread: >>> >>> "Right. Whenever possible." >>> >>> It is useful to learn about RAT and the committers tools, although it >> doesn't apply to my situation. My question was not about how to make the >> notice, it was about how Greg seemed to stamp it onto every textual > artifact >> he committed to SVN. >>> >>> Two lessons: >>> 1. I need to be careful about answering the (actual) question being > asked. >>> 2. When I ask questions, I need to be very clear what the question is > (and >> still risking that won't be the question answered). >>> >>> - Dennis >>> >>> -----Original Message----- >>> From: Shane Curcuru [mailto:[email protected]] >>> Sent: Thursday, July 28, 2011 19:19 >>> To: [email protected] >>> Subject: Re: Q: Notices in Code >>> >>> Apache RAT is in the incubator, and some projects use it to do source >>> code license checking and the like: >>> >>> http://incubator.apache.org/rat/ >>> >>> Note that the committers repository has two directories with other, much >>> simpler (but possibly useful) tools about checking or changing licenses >>> or other standard chunks of text in masses of source code: >>> >>> https://svn.apache.org/repos/private/committers >>> >>> /relicense >>> and >>> /tools >>> >>> - Shane >>> >>
