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 Plain View
Bigtop >> mail # dev >> [DISCUSS] Using --signoff option with git am when committing patches


+
Mark Grover 2013-09-04, 21:58
+
Konstantin Boudnik 2013-09-04, 22:03
+
Mark Grover 2013-09-04, 22:05
+
Roman Shaposhnik 2013-09-08, 05:56
+
Mark Grover 2013-09-08, 22:00
Copy link to this message
-
Re: [DISCUSS] Using --signoff option with git am when committing patches
And, about your former point:

Our git format-patch policy for patches ensures that the name of the actual
contributor who committed the code shows up on the commit message when
doing git log. However, I think it will be useful to see which committer
committed that patch on behalf of the contributor. That's exactly the
problem "--sign-off" solves.

Linux kernel<http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/SubmittingPatches?id=HEAD>,
for example, has a policy to use --sign-off flag and the same applies to
contributing to the git
project<http://git.kernel.org/cgit/git/git.git/tree/Documentation/SubmittingPatches?id=HEAD>
.
And, there are some other benefits too, listed here:
http://stackoverflow.com/questions/1962094/what-is-the-sign-off-feature-in-git-for

Mark
+
Andrew Purtell 2013-09-15, 20:28
+
Mark Grover 2013-09-15, 22:20
+
Konstantin Boudnik 2013-09-16, 04:23
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