Mercurial: Difference between revisions

At the time of the mid-term or final review (or whenever the mentor requires it) students should prepare their code  

for review and possibly inclusion into the main development branch. To this end students should:

<li> prepare a full log of their changes, listing files that have been touched  

  and including a summary of the purpose of those changes. If students have been following  

  <code> hg log --style=changelog --no-merges --user student-name </code><br>

  this message should be edited so that  

  <li> each touched file appears only once </li>

  <li> changes that were backed out should not be mentioned (like changeset "H" in the above example) </li>

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]].

</ol>

== Mercurial Tips for SoC mentors ==

<code>