hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Todd Lipcon <t...@cloudera.com>
Subject Re: svn commit: r1304067 - in /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project: ./ bin/ conf/ hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/resources/ hadoop-mapreduce-examples/ hadoop-yarn/hadoop-yarn-site/ hadoop-yarn/ha
Date Fri, 23 Mar 2012 00:21:18 GMT
On Thu, Mar 22, 2012 at 5:03 PM, Owen O'Malley <omalley@apache.org> wrote:
> To me, I'd much much rather have the human readable description of what is
> being fixed and I mostly could care less about which subversion commit it
> corresponds to. I'd be all for using the CHANGE.txt description as the
> commit message for both trunk and the branches.

+1. I never even use the svn merge command to merge between branches.
I just apply the patch separately to each branch. The svn metadata on
single-patch merges seems pretty much useless, best I can tell.

-Todd
-- 
Todd Lipcon
Software Engineer, Cloudera

Mime
View raw message