Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change 
notification.

The "Hive/HowToCommit" page has been changed by JohnSichi.
http://wiki.apache.org/hadoop/Hive/HowToCommit?action=diff&rev1=3&rev2=4

--------------------------------------------------

  
  == Reject ==
  
- Patches should be rejected which do not adhere to the guidelines in 
HowToContribute.  Committers should always be polite to contributors and try to 
instruct and encourage them to contribute better patches.  If a committer 
wishes to improve an unacceptable patch, then it should first be rejected, and 
a new patch should be attached by the committer for review.
+ Patches should be rejected which do not adhere to the guidelines in 
[[Hive/HowToContribute]].  Committers should always be polite to contributors 
and try to instruct and encourage them to contribute better patches.  If a 
committer wishes to improve an unacceptable patch, then it should first be 
rejected, and a new patch should be attached by the committer for review.
  
  == Commit ==
  
@@ -42, +42 @@

   1. End-user documentation, versioned with releases; and,
   1. The website.  This is maintained separately in subversion, republished as 
it is changed.
  
- To commit end-user documentation changes to trunk or a branch, ask the user 
to submit only changes made to the *.xml files in {{{src/docs}}}. Apply that 
patch, run {{{ant docs}}} to generate the html, and then commit.  End-user 
documentation is only published to the web when releases are made, as described 
in HowToRelease.
+ To commit end-user documentation changes to trunk or a branch, ask the user 
to submit only changes made to the *.xml files in {{{src/docs}}}. Apply that 
patch, run {{{ant docs}}} to generate the html, and then commit.  End-user 
documentation is only published to the web when releases are made, as described 
in [[Hive/HowToRelease]].
  
  To commit changes to the website and re-publish them: {{{
  svn co https://svn.apache.org/repos/asf/hadoop/hive/site

Reply via email to