AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Tortoisehg global ignore1/31/2024 Students should publish their work as it progresses in a public repository. This section is meant to provide tips for Summer of Code students working on new Octave features. If your patch file is larger than the upload limit, you can compress it before uploading. Upload bug42424.patch to the bug or patch tracker.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 # Get help text - = get_help_text (name) + = get_better_help_text (name) # Take action depending on help text format switch (lower (format)) To push to a repository, if you have push rights to that repository, you can see what's going out with hg out and then if you're happy with it you can hg push.That way, local clones on stable don't have to switch branches before merging. It's best to run this only in local clones that are already on the default branch. To merge changes from stable to default hg merge stable.Do a pull and up to get that, then do a pull and up in your individual clone directories to get it there. Wait for a maintainer to apply it with your name, then if you do hg in in your main Octave directory it'll show up as an incoming change. Type hg export >/tmp/my.patch and upload that file into the bug discussion. Build again so your build gets the latest hg id. Then hg commit and type a summary and context for your change. Then build again to make sure things haven't broken. 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.Accept feedback from the bug discussion and iterate your patch. You can also copy-paste it into a bug discussion using verbatim tags if the patch is small enough. To circulate work-in-progress bugfixes: first cd to the relevant local clone, then edit the relevant files, verify that it builds, then hg diff >/tmp/my.wip.patch and then upload that file to the bug tracker discussion.To work on the stable branch instead of the default branch, make a local clone called "stable", then cd to it and hg update stable.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 prevent a fresh download of gnulib, you can specify the path to the first Octave directory's gnulib if you want. Then you can cd into the new directory and run bootstrap, configure, make. You'll need to cd to the correct directory first. To make a local clone, you can clone from your main Octave repository on your computer to another directory like this: hg clone octave myfeature which will clone the Octave directory into a new directory called "myfeature".To update on a regular basis, you can do hg pull -u or hg pull & hg up.You can then bootstrap, configure and make, make check, maybe make install. This section gives several frequently used Mercurial commands and sequences. 4.2 Staying up-to-date with the main repository.3 Creating and submitting patches (changesets).
0 Comments
Read More
Leave a Reply. |