Diff for /wikisrc/Wifi_renewal_on_hg.mdwn between versions 1.2 and 1.3

version 1.2, 2020/04/26 16:12:42 version 1.3, 2020/04/26 16:35:39
Line 4  The wifi renewal project is trying to sy Line 4  The wifi renewal project is trying to sy
   
 ## Why hg?  ## Why hg?
   
 The project started with a traditional cvs branch, but as we will be moving to mercurial anyway (and this "branch" could live for quite some time, even accross the general repo switch), it is a good test case for the hg environment and also nice practice for the developers involved.  The project started with a traditional CVS branch, but as we will be moving to mercurial anyway (and this "branch" could live for quite some time, even across the general repo switch), it is a good test case for the hg environment and also nice practice for the developers involved.
   
 The developement uses a "topic", which is a kind of lightweight branch that goes away after the project finished. The hg documentation includes  The development uses a "topic", which is a kind of lightweight branch that goes away after the project finished. The hg documentation includes
 an [introduction to topics](https://www.mercurial-scm.org/doc/evolution/tutorials/topic-tutorial.html).  an [introduction to topics](https://www.mercurial-scm.org/doc/evolution/tutorials/topic-tutorial.html).
   
 ## Helping with testing  ## Helping with testing
Line 22  Now enable the 'topic' extension by addi Line 22  Now enable the 'topic' extension by addi
     [extensions]      [extensions]
     topic=      topic=
   
 to the .hg/hgrc file in your clone dir and then update to the 'wifi' topic:  to the .hg/hgrc file in your clone directory and then update to the 'wifi' topic:
   
     > hg up wifi      > hg up wifi
   
 ## Helping with developement  ## Helping with development
   
 As a developer, you should start with an annonhg clone as well, as that uses 'clonebundles' and the CDN to get your clone faster.  As a developer, you should start with an anonhg clone as well, as that uses 'clonebundles' and the CDN to get your clone faster.
   
 The developement happens using the topic and evolve extensions, which unfortunately slows down some hg operations.  The development happens using the topic and evolve extensions, which unfortunately slows down some hg operations.
   
 After initial cloning (see above) you will have to edit your global ~/.hgrc and the clone local .hg/hgrc files. Here is my ~/.hgrc:  After initial cloning (see above) you will have to edit your global ~/.hgrc and the clone local .hg/hgrc files. Here is my ~/.hgrc:
   
Line 48  After initial cloning (see above) you wi Line 48  After initial cloning (see above) you wi
     pager=      pager=
     rebase=      rebase=
   
 The .hgignore file referened there tells hg to leave editor backups and compiled kernels alone. Mine looks like:  The .hgignore file referenced there tells hg to leave editor backups and compiled kernels alone. Mine looks like:
   
     syntax: glob      syntax: glob
     *~      *~
     *.o      *.o
     sys/arch/amd64/compile/*      sys/arch/amd64/compile/*
   
 Finaly the clone local config (.hg/hgrc) looks like this:  Finally the clone local config (.hg/hgrc) looks like this:
   
     [paths]      [paths]
     default = ssh://hgmaster.netbsd.org//repo/src-draft      default = ssh://hgmaster.netbsd.org//repo/src-draft
Line 63  Finaly the clone local config (.hg/hgrc) Line 63  Finaly the clone local config (.hg/hgrc)
     [phases]      [phases]
     publish=false      publish=false
   
 This directs normal pushes to the src-draft repository and prevents publishing (that is what "merging the branch to HEAD" would have been in cvs). When it is time to do that, a "final" push will be done that moves the changes to the src-public repository (and empties the topic, which will make it vanish on next update).  This directs normal pushes to the src-draft repository and prevents publishing (that is what "merging the branch to HEAD" would have been in CVS). When it is time to do that, a "final" push will be done that moves the changes to the src-public repository (and empties the topic, which will make it vanish on next update).

Removed from v.1.2  
changed lines
  Added in v.1.3


CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb