Owen O'Malley wrote:
On Mar 5, 2009, at 11:41 AM, Brian Bockelman wrote:
Dumb comment:
Not really
Although I know what issue HADOOP-3638 is referring to, it's not a
great way for the branch name to be self-descriptive.
Actually, I find it much more natural to label branches with jira
numbers than names. It might help if there is a HADOOP-*.readme at the
top level that describes the branch in words.
Bone. Branch is in, with covering text
https://svn.apache.org/repos/asf/hadoop/core/branches/HADOOP-3628/HADOOP-3628.txt
Now that I'm sure that the text has appeared in a branch and not trunk,
I will leave the machine to commit all the other changes. That includes
a bit more than just the 3268 patch, as this machine contains most of my
little extra diagnostics tweaks that has crept in; more stack traces and
information on who is refusing to accept connections on
ConnectionRefused exceptions (that happens enough that I should make a
utility method, one that also includes the local hostname/address for
extra diganostics)
