File:  [NetBSD Developer Wiki] / wikisrc / Wifi_renewal_on_hg.mdwn
Revision 1.3: download - view: text, annotated - select for diffs
Sun Apr 26 16:35:39 2020 UTC (2 years ago) by wiz
Branches: MAIN
CVS tags: HEAD
Fix some typos, uppercase CVS.

#How to help with the Wifi renewal "branch" in hg

The wifi renewal project is trying to sync our sys/net80211 with FreeBSD as far as possible, to allow easier sharing of drivers.

## 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 across the general repo switch), it is a good test case for the hg environment and also nice practice for the developers involved.

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

## Helping with testing

** Note that this project is not ready for general testing yet! **

If you just want to check out the wifi project source and build your own test kernel for it, you simply start by cloning the repository from anonhg:

    > hg clone

Now enable the 'topic' extension by adding


to the .hg/hgrc file in your clone directory and then update to the 'wifi' topic:

    > hg up wifi

## Helping with development

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 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:

    user=Martin Husemann <>
    color = no
    ignore = ~/.hgignore
    default:pushrev = .

The .hgignore file referenced there tells hg to leave editor backups and compiled kernels alone. Mine looks like:

    syntax: glob

Finally the clone local config (.hg/hgrc) looks like this:

    default = ssh://
    final = ssh://

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

CVSweb for NetBSD wikisrc <> software: FreeBSD-CVSweb