Revision as of 04:22, 16 August 2013 (edit)
Cdf (talk | contribs)
 (→‎Staying up-to-date with the main savannah repository)
← Older edit
Latest revision as of 17:15, 4 April 2024 (edit) (undo)
Mmuetzel (talk | contribs) 
 (→‎Creating and submitting patches (changesets):  Replace mirror by link to main repository)
 
[[wikipedia:Mercurial]] (sometimes referred to as {{codeline|hg}}) is the version control tool used by Octave.
[https://www.mercurial-scm.org Mercurial] (sometimes referred to as {{codeline|hg}}) is the source code management system used for Octave development.
This page contains some helpful commands to use when interacting with the GNU Octave mercurial repository.
== Patches ==
Everybody is free to '''run, copy, distribute, study, change and improve'''<ref>https://www.gnu.org/philosophy/free-sw.en.html</ref> Octave's source code, given in the main repository at https://www.octave.org/hg/octave.  Use Mercurial to get the latest version of Octave <pre>hg clone https://www.octave.org/hg/octave</pre>
When you do not have push permissions to the repository (you cannot add your changes using mercurial itself) and you have a modification to the current GNU Octave code,  you have to generate a patch (or changeset) so developers with permissions can include them in the code. The overview of the process is as follows
# Change the code and test that your changes do work (write tests, that's the best!).
# Create the changeset (instructions below).  
# Post your patch in the [https://savannah.gnu.org/patch/?group=octave Patch tracker].
=== Before starting ===
== Workflow reference ==
The way patches are generated uses an [http://mercurial.selenic.com/wiki/MqExtension extension] of mercurial and therefore you need to prepare your .hgrc file to use it.
This section gives several frequently used Mercurial commands and sequences.
If you do not have a .hgrc file, just create one in your home directory. In Windows, this is something like "C:\Documents and Settings\your_name\Mercurial.ini"
Add the following code to that file:
* Initial clone: <pre>hg clone https://hg.savannah.gnu.org/hgweb/octave/</pre>
  [extensions]
You can then bootstrap, configure and make, make check, maybe make install.
  hgext.mq =
 
  hgext.pager =
* To update on a regular basis, you can do <pre>hg pull -u</pre> or <pre>hg pull && hg up</pre>
  color =
 
* To make a ''local clone'', you can clone from your main Octave repository on your computer to another directory like this: <pre>hg clone octave myfeature</pre> which will clone the Octave directory into a new directory called "myfeature". You'll need to cd to the correct directory first. Then you can cd into the new directory and run bootstrap, configure, make. To prevent a fresh download of gnulib, you can specify the path to the first Octave directory's gnulib if you want.
 
It is best practice to make a new clone directory for each feature or bugfix you work on, which makes recovery from mistakes much easier.
 
* To work on the stable branch instead of the default branch, make a local clone called "stable", then cd to it and <pre>hg update stable</pre>
 
* To circulate work-in-progress bugfixes: first cd to the relevant local clone, then edit the relevant files, verify that it builds, then <pre>hg diff &gt;/tmp/my.wip.patch</pre> and then upload that file to the bug tracker discussion. You can also copy-paste it into a bug discussion using ''verbatim'' tags if the patch is small enough. Accept feedback from the bug discussion and iterate your patch.
 
* When you're ready to commit your fix, first pull and update your main Octave directory from Savannah, then pull and update your local clones. Then build again to make sure things haven't broken. Then <pre>hg commit</pre> and type a summary and context for your change. Exit the editor, saving when it prompts. Build again so your build gets the latest hg id. Type <pre>hg export &gt;/tmp/my.patch</pre> and upload that file into the bug discussion. Wait for a maintainer to apply it with your name, then if you do <pre>hg in</pre> in your main Octave directory it'll show up as an incoming change. Do a pull and up to get that, then do a pull and up in your individual clone directories to get it there.
 
* To merge changes from stable to default <pre>hg merge stable</pre>. It's best to run this only in local clones that are already on the default branch. That way, local clones on stable don't have to switch branches before merging.
 
* To push to a repository, if you have push rights to that repository, you can see what's going out with <pre>hg out</pre> and then if you're happy with it you can<pre>hg push</pre>.
 
==Tutorials==
Joel Spolsky's Mercurial tutorial: [https://hginit.github.io/01.html https://hginit.github.io/01.html]
 
{{Note|[https://tortoisehg.bitbucket.io/ TortoiseHg] is a GUI for Mercurial and it is especially recommended for users doing their first steps with source code management systems.  Linux, macOS, and MS Windows are supported.}}
 
== Creating and submitting patches (changesets) ==
 
If you want to share your modifications, for example to fix a nasty '''bug #42424''', you cannot just submit your changes to Octave's main repository.  You have to generate a '''patch (or changeset)''' so other Octave developers can include them into Octave's source code.
 
# Get the latest version of Octave (or some Octave package) <pre>hg clone https://www.octave.org/hg/octave</pre> or when already cloned <pre>hg pull && hg update</pre>
# Make your changes (fix bug #42424) and save them.  '''Make sure that your changes don't introduce new bugs!'''  Thus it is recommended to [[Building | build Octave]] and to [[Tests | run Octave's test suite]] before proceeding.<br>{{Warning|Please follow the [[Contribution guidelines]] for C/C++ or Octave code files!}}
# Commit your changes <pre>hg commit</pre> Mercurial will open your default editor<ref>To set your default Mercurial editor, read https://www.mercurial-scm.org/wiki/editor .</ref> and ask you for a commit message.  Please follow the [[commit message guidelines]], e.g. <syntaxhighlight lang="text">help.m: Display relevant topics first (bug #42424)
 
* scripts/help/help.m: Describe what you changed to display relevant topics
  first.  The maximal line width is 80 characters.</syntaxhighlight>
# Export the changes <pre>hg export -r tip -o bug42424.patch</pre> The final patch for submission will look like this {{file|bug42424.patch|<syntaxhighlight lang="diff"># HG changeset patch
# User Awesome Hacker <awesome@hacker.com>
# Date 1591780091 -32400
#      Wed Jun 10 18:08:11 2020 +0100
# Node ID 68c698c4f2fd98bf2d48234bd1da99e91763114f
# Parent  f5c9bb5955e7c9fddef5c3c3f115201e11b43b79
 
help.m: Display relevant topics first (bug #42424)
 
* scripts/help/help.m: Describe what you changed to display relevant topics
  first.  The maximal line width is 80 characters.
 
diff -r f5c9bb5955e7 -r 68c698c4f2fd scripts/help/help.m
--- a/scripts/help/help.m	Tue Jun 09 14:11:13 2020 -0700
+++ b/scripts/help/help.m	Wed Jun 10 18:08:11 2020 +0900
@@ -99,7 +99,7 @@ function retval = help (name)
     endif
   
   
 [pager]
     ## Get help text
 pager = LESS='FSRX' less
-    [text, format] = get_help_text (name);
 attend = help, annotate, cat, diff, export, glog, log, qdiff, status, outgoing, incoming
+    [text, format] = get_better_help_text (name);
   
   
 ## Colours I like
     ## Take action depending on help text format
 [color]
     switch (lower (format))
 status.modified = magenta bold
 
  status.added = green bold
</syntaxhighlight>}}
 status.removed = red bold
# Upload {{Path|bug42424.patch}} to the [https://savannah.gnu.org/bugs/?group=octave bug] or [https://savannah.gnu.org/patch/?group=octave patch] tracker. If your patch file is larger than the upload limit, you can compress it before uploading. Please use a free format!
 status.deleted = cyan bold
 
  status.unknown = gray  bold
== Mercurial Tips for SoC students ==
 status.ignored = gray bold
 
This section is meant to provide tips for [[Summer of Code]] students working on new Octave features.
 
Students should publish their work as it progresses in a public repository. In this section we use for example <code>public.server.org/octave</code>.
 
=== Using bookmarks ===
 
[https://www.mercurial-scm.org/wiki/Bookmarks Bookmarks] are useful for identifying a series of commits.  They are a "lightweight" solution to [https://www.mercurial-scm.org/wiki/NamedBranches named branches], which are not automatically updated for example.  To create a bookmark <code>my-gsoc</code> use
 
<syntaxhighlight lang="bash">
hg clone https://www.octave.org/hg/octave
hg bookmark my-gsoc
</syntaxhighlight>
 
To make the bookmark visible in the public repository use
 
<syntaxhighlight lang="bash">
hg push --bookmark ssh://student@public.server.org/octave
</syntaxhighlight>
 
=== Staying up-to-date with the main repository ===
 
Octave development does not stand still while the students development proceeds.  Octave's main repository gets updated, too.  The following commands can be used to get these updated to the students clone of the main repository:
 
<syntaxhighlight lang="bash">
hg pull https://www.octave.org/hg/octave   # Get latest remote "tip"
hg update -r my-gsoc                       # Activate bookmark "my-gsoc"
hg merge tip                               # Merge  "tip" into "my-gsoc"
hg commit -m "maint: merge default to my-gsoc"
hg push ssh://student@public.server.org/octave
</syntaxhighlight>
 
=== Preparing for code reviews ===
 
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 repository.
The only part that is important is the extensions. The rest is to make hg behave in a fancy way (recommended).
# Create a full log of changes <pre>hg log --template=changelog --no-merges --user student-name</pre> If students have been following the [[Commit message guidelines]] the output is a good starting point for the commit message in the next step.  Some manual post-processing might be necessary:
#* Each touched file should appear only once.
#* Do not mention backed-out commits.
# Prepare a singe patch (changeset) including all code that should be submitted for review <syntaxhighlight lang="bash">
hg pull https://www.octave.org/hg/octave   # Get remote "tip" and "@"
hg update -r @                             # Activate    bookmark "@"
hg merge my-gsoc                           # Merge "my-gsoc" into "@"
hg commit
hg export -r tip -o mid-term-review.patch
</syntaxhighlight> The file {{Path|mid-term-review.patch}} can uploaded to the [https://savannah.gnu.org/patch/?group=octave patch tracker]. <br/> Finally, there is a subtle difference between <code>"tip"</code>, which is a reference to the (local or remote) changeset added to the repository most recently and the bookmark <code>"@"</code> used by the Octave developers to point to the latest remote changeset.  Often both refer to the very same changeset and they can used interchangeably.
=== Creating changesets with hg ===
== Example Mercurial configuration ==
==== Simple way ====
* Update to the latest revision. 
<pre> hg up </pre>
* Make your changes and save. 
* Commit your code following the [[commit message guidelines]]. 
<pre> hg ci </pre>
* Export the modifications. 
<pre> hg export -r tip -o mypatch.patch </pre>
* Save the output to a file and upload it tot he patch tracker.
==== Using the MQ extension ====
Place the following file in your home directory, e.g. {{Path|/home/username/.hgrc}}.
In the repository you can start a patch by doing 
 hg qnew mychangeset
You can further edit your files... if you do, you need your patch to know about these changes. To do that execute
{{File|.hgrc|<syntaxhighlight lang="ini">
 hg qrefresh
[ui]
username = Your Name <your@email>
Once you think you have all the changes that make your patch complete you can export your patch
[extensions]
 hg qdiff > mychangeset.patch
color =
histedit =
pager =
rebase =
strip =
Now you can do (at least) two things
[pager]
* Apply your patch to your copy (it will differ form the repository and you will have to merge somehow...). To do it run
pager = LESS='FSRX' less
 hg qfinish tip
attend = help, annotate, cat, diff, export, glog, log, outgoing, incoming
* Forget the changes and go back to the unpatched version of the code.
 hg qrefresh
 hg qpop
 hg qfinish tip
The file mychangeset.patch contains your changes.
[diff]
showfunc = True
[color]
mode = terminfo
== Mercurial Tips for SoC students ==
## Custom colors
color.gray = 244
color.orange = 202
color.lightyellow = 191
color.darkorange = 220
color.brightyellow = 226
 
status.modified = magenta bold
status.added = green bold
status.removed = red bold
status.deleted = cyan bold
status.unknown = gray bold
status.ignored = gray bold
 
## Colors for each label
log.branch = cyan
log.summary = lightyellow
log.description = lightyellow
log.bookmark = green
log.tag = darkorange
log.graph = blue
 
## Colors for each phase
changeset.secret = blue bold
changeset.draft  = red bold
changeset.public = orange
 
desc.here = bold blue_background
 
[bookmarks]
track.current = True
 
[alias]
glog = log --graph
top  = log --graph -l
</syntaxhighlight>}}
 
== Tips for working with TortoiseHg ==
 
TortoiseHg is a multi-platform graphical user interface for Mercurial repositories. It allows to perform many hg operations using the context menu and toolbar buttons. That might make it easier to get used to working with Mercurial.
 
=== Activate the "mq" extension ===
 
The "mq" extension allows to modify (local) changesets after they have been committed. It also allows to rebase changes to a new parent or to strip changes completely.
The "mq" extension does *not* allow to modify pushed changes.
 
To activate the "mq" extension in TortoiseSVN, open the settings, select "Extensions" on the global settings tab and activate the checkbox next to "mq".
<!--This page is addressed to SOCIS or GSoC applicants contributing to Octave.-->
The most useful feature of that extension is probably to update an existing changeset. For this, select "Modify History" -> "Import to MQ" in the right click menu of the respective changeset. After updating some local files or changing the commit message, hit the "QRefresh" button. Finish the patch by selecting "Modify History" -> "Finish Patch" from the right click menu of the respective changeset.
Students should publish their work as it progresses in a public repository 
merging regularly the main savannah repository to facilitate merging back their 
code at the end of the project.  
Here are some useful hg commands that can be used to do this.
=== Getting started ===
=== Rebase a change to a current tip ===
<!--[[File:Hg-student-start.png]]-->
<ol>
<li> Clone the main Octave repository at savannah:<br>
 <code> hg clone http://www.octave.org/hg/octave </code> </li>
<li> Create a new bookmark:<br>
 <code> hg bookmark student-bookmark-name </code> </li>
<li> Make the bookmark visible in the public repo, assuming the public repo is at <code>public.server.org/octave</code><br>
 <code> hg push --bookmark ssh://student@public.server.org/octave </code> </li>
</ol>
=== Staying up-to-date with the main savannah repository ===
Sometimes a change in the upstream repository might make it necessary to rebase a changeset to a new parent. There are several ways to achieve this. The ways described here might not be the most elegant ones. Any editor is welcome to add onto this.
<!-- After working for a while, the public repo should look like the following picture. -->
Strip and commit:
As the students development proceeds,
# Pull changes from the upstream repository.
the savannah repository gets updated, too.  
# Before updating to the new tip, strip the local changes by selecting "Modify History" -> "Strip..." from the right click menu. In the dialog, select "Do not modify working copy during strip (-k/--keep)".
To avoid having the two branches diverging too much, which can
# Update to the new tip (maybe in incremental steps).
lead to conflicts when the final merge is done, students should
# Commit the local changes in a "fresh" changeset. This has the drawback that any commit message might be lost. But it often works even if other approaches fail.
keep their public repo up-to-date with the recent changes, 
the following commands can be used for this:<br/>
<ol>
<!--[[File:Hg-student-flow1.png]] <br/>-->
<li> Download new changes from the main line of development <br/>
<code> hg pull http://www.octave.org/hg/octave </code> </li>
<li> Merge the main line of development into the feature branch <br/>
<code> hg up -r student-bookmark-name </code> <br/>
<!--[[File:Hg-student-flow2.png]] <br/>-->
<code> hg merge @ </code> </li>
<li> Apply the change and publish it
<code> hg commit -m "periodic merge of default branch into my branch" </code> 
<!--[[File:Hg-student-flow3.png]] <br/>-->
<code> hg push ssh://student@public.server.org/octave </code></li>
</ol>
=== Preparing for code reviews ===
Un-apply and re-apply:
At the time of the mid-term or final review (or whenever the mentor requires it) students should prepare their code 
# Pull changes from the upstream repository.
for review and possibly inclusion into the main development branch. To this end students should:
# Before updating to the new tip, import the local changeset to mq by selecting "Modify History" -> "Import to MQ" in the right click menu.
<ol>
# You might want to refresh the changeset with local changes.
<li> prepare a full log of their changes, listing files that have been touched 
# Un-apply the patch by selecting "Modify History" -> "Unapply Patch" from the right click menu. If there are other, un-committed changes in the local repository, you might want to select "Tolerate non-conflicting local changes (--keep-changes)" in the "Modify History" -> "MQ Options" dialog from the right click menu beforehand.
 and including a summary of the purpose of those changes. If students have been following 
# Update to the new tip.
 the [[Commit message guidelines]] the following command will give a good starting point<br>  
# Select the previously unapplied patch on top of the revision graph and re-apply it by using the "Reapply Patch" option in the right click menu. This has the advantage that a commit message will be retained. But re-applying the patch might fail if there were changes in the upstream repository that made the patch incompatible.
 <code> hg log --style=changelog --no-merges --user student-name </code><br>
 this message should be edited so that 
 <ol   style="list-style-type: lower-roman;">
 <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>
 </ol>
The main  purpose of this log is to make it easy, not only for the main mentor, but also for other developers who
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
  <ol>
  <code>hg pull </code>
  </ol> </li>
</ol>
== Mercurial Tips for SoC mentors ==
Rebase:
<code>
# Pull changes from the upstream repository.
hg pull http://student.repo.url
# Select the local changeset that you'd like to rebase.
</code>
# Hold down the Ctrl key and select the changeset that should be the new parent of the local changeset (probably the new tip).
# Right-click the changeset of the new parent and select "Rebase...".
# The default settings are often times fine. This process has the advantage that a commit message will be retained and it often times resolves conflicts automatically. But it doesn't work if there are any un-committed local changes.
<code>
== Footnotes ==
hg pull http://www.octave.org/hg/octave
</code>
<code>
<references/>
hg up -r @
</code>
<code>
== External links ==
hg merge student_bookmark
</code>
<code>
* https://hginit.com/ -- Mercurial tutorial
hg log --style=changelog --user student
* https://www.mercurial-scm.org/wiki/Tutorial -- Mercurial tutorial
</code>
* https://www.mercurial-scm.org/wiki/QuickStart -- Mercurial quick start
* https://tortoisehg.bitbucket.io/ -- TortoiseHg is a GUI for Mercurial (Linux, macOS, MS Windows)
[[Category:Development]]
[[Category:Development]]