Mercurial: Difference between revisions

362 bytes added ,  16 August 2013
no edit summary
No edit summary
Line 126: Line 126:
have not been closely following the progress of the project to quickly understand where to look at in the code to evaluate it, but it will also be used as the commit message for the merge changeset, so it should itself comply with the [[Commit message guidelines]].
have not been closely following the progress of the project to quickly understand where to look at in the code to evaluate it, but it will also be used as the commit message for the merge changeset, so it should itself comply with the [[Commit message guidelines]].
<li> prepare a merge changeset including all the code that should be submitted for review
<li> prepare a merge changeset including all the code that should be submitted for review
   <ol>
   <ol style="list-style-type: lower-roman;">
   <code>hg pull </code>
  <li> pull from the main repository<br/>
   <code>hg pull http://www.octave.org/hg/octave</code></li>
  <li> pull from the main repository<br/>
  <code>hg pull http://www.octave.org/hg/octave</code></li>
   </ol> </li>
   </ol> </li>
</ol>
</ol>


== Mercurial Tips for SoC mentors ==
== Mercurial Tips for SoC mentors ==
Will fill in this section after trying out the above procedure at least once with a student
and actually pushing his changes to the main repo.


<!---
<!---
349

edits