Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop >> mail # dev >> Dropping CHANGES.txt?


Copy link to this message
-
Re: Dropping CHANGES.txt?
On 11/21/2011 11:49 AM, Matt Foley wrote:
> The advantage of CHANGES.txt is that it merges when the branch merges.  So
> as long as the developers stick to reasonably normal merge and commit
> processes, it truly reflects what is in the current state of any given
> branch, at least at the level of changes related to Jiras.

I agree.  Its redundancy makes it valuable.  I often use CHANGES.txt
diffs to double-check that I've merged the right revision to a branch.

Doug
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB