Dear Wiki user, You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.
The "HowToContribute" page has been changed by ArpitAgarwal: https://wiki.apache.org/hadoop/HowToContribute?action=diff&rev1=91&rev2=92 Comment: Cleanup for previous edit Patches for trunk should be named according to the Jira: '''jira-xyz.patch''', eg hdfs-1234.patch. - Patches for a non-trunk branch should be named '''jira-xyz-branch.patch''', eg hdfs-123-branch-2.patch. The branch name suffix should be the exact name of a Subversion branch under hadoop/common/branches/, such as "branch-0.20-security". Please note that the Jenkins pre-commit build is only run against trunk. + Patches for a non-trunk branch should be named '''jira-xyz-branch.patch''', eg hdfs-1234-branch-0.23.patch. The branch name suffix should be the exact name of a Subversion branch under hadoop/common/branches/, such as "branch-0.23". Please note that the Jenkins pre-commit build is only run against trunk. It's OK to upload a new patch to Jira with the same name as an existing patch. If you select the "Activity>All" tab then the different versions are linked in the comment stream, providing context. However many contributors find it convenient to add a numeric suffix to the patch indicating the patch revision. e.g. hdfs-1234.01.patch, hdfs-1234.02.patch etc. @@ -248, +248 @@ Some things to note: * the optional cmd parameters will default to the ones in your {{{PATH}}} environment variable - * the {{{grep}}} command must support the -o flag (Both GNU grep bundled and BSD grep do so) + * the {{{grep}}} command must support the -o flag (Both GNU grep and BSD grep support it) * the {{{patch}}} command must support the -E flag Run the same command with no arguments to see the usage options.
