Do I have to wait until a patch is committed before I can submit another one?
Nope. Are you using the "q" commands (qnew, qpop, qpush, etc)? If so, then you can just create patch on top of patch, on top of patch.
Lets say you have add_tdrtab all set:
% hg qap add_tdrtab
and you want to create another one for "add_foobar" on top of that:
% hg qnew -e add_foobar <edit your commit message>
then make some changes to some files, and qrefresh the patch:
% hg qrefresh
You'll see both applied:
% hg qapplied add_tdrtab add_foobar
Then you can qpush and qpop them on and off the stack if you need to make changes to one or the other of them.
Not sure I explained that properly, but play with it a bit and let me know if you need clarification.
How do I keep the 'chirp' folder up-to-date? Is there some command to update it?
Once something has been committed upstream, you can pop and delete the patch from your tree. Here's an overly verbose example:
% hg qapplied # Show which patches are applied to my tree add_tdrtab # My add_tdrtab patch is applied % hg qpop # "Pop" or unapply the top-most patch % hg qapplied # Now it's no longer applied % hg qunapplied # It's "unapplied" add_tdrtab % hg qdel add_tdrtab # Delete it from my patch queue % hg qunapplied # Now it's gone-gone %
Then you can pull the changes from the upstream repository and update your local tree:
% hg pull -u
At that point, you'll be up-to-date with my tree.
Would it be OK to reorganize the Settings tabs for the UV-5R?
Sure. I think I had some method to my madness originally, but I don't really recall what my plan was. The "Other Settings" was intended to house everything that was in the auxiliary block, which are only settable in the weird way in the VIP software. What did you have in mind?