(I'm on both sides of the upstream/downstream divide)
It's a good idea to have a per-directory-tree metadata file that can
provide information about the tree where it is found, like TEST.ROOT but
more general and extensible. Here at Google we actually have files named
METADATA - this makes it obv
On 2015-09-17 18:24, Martin Buchholz wrote:
flush with success, I ran blessed-modifier-order on the entire JDK forest,
and it seems to work fine.
But we want to leave out code maintained elsewhere. How to identify that?
As far as I know, the only way to figure out if code is maintained
elsewh
flush with success, I ran blessed-modifier-order on the entire JDK forest,
and it seems to work fine.
But we want to leave out code maintained elsewhere. How to identify that?
Below are changes inside javadoc, which seem fine to me.
$ hg tcommand hg diff | g '^[+-] *\*'
- * Access to f
