[chirp_devel] [PATCH 1 of 1] [KG-UVD1P KG-UV6] Add support for tx inhibit
IZ3GME Marco
Mon Nov 5 10:58:48 PST 2012
Hi Johan
first I suggest you to use tortoisehg as gui interface to mercurial.
On 05/11/2012 17:53, Johan Adler wrote:
> OK, I have applied the patch using:
>
> jadler at server:~/usb-minne/Dokument/ssa-amatörradio/chirp/chirp.hg$
> patch -p1 < ../devel-121105-0.diff
>
It would be better to import it to mercurial with
hg import /path/to/mail/file
(but I use to do this using tortoisehg)
I found the guide http://mercurial.selenic.com/guide/ very useful when I
started using mercurial.
> The patched wouxun.py looks OK to me. How do I run this local copy of
> the development version instead of the installed daily build (Ubuntu,
> pulled from repository)? Running <chirp base>/chirpw.py seems to use
> the installed version instead. Do I have to remove the installed daily
> build and manually install the patched development version?
You can run the development version running it's chirpw
cd /usb-minne/Dokument/ssa-amatörradio/chirp/chirp.hg
./chirpw
but you can also load a "chirp module" at runtime using menu File - Load
module (you must enable developer functions in help menu first)
>
> You seem to have used "diff --git a/chirp/wouxun.py b/chirp/wouxun.py"
> to produce the diff. Is there a significant reason not to use the diff
> command of hg, e.g. "hg diff chirp.hg/ > wouxun-121103-01.diff"? The
> latter is aware of development tree version, and I guess it is more
> likely to gracefully handle attempts to apply the patch to a source
> tree that has not been updated.
I first committed the changes to my local hg repository and then sent
the newly created revision to the list as a PatchBomb.
Hope this can help
73 de IZ3GME Marco
More information about the chirp_devel
mailing list