I was just about to recommend CHIRP to a friend with a T7H, but I realized release 0.2.3 doesn't appear to include T7H support, as evidenced by the test report and lack of a ict7h.py file in the tarball. Is it being held back due to limited field testing at this point?

On Wed, Jul 18, 2012 at 7:50 PM, Dan Smith <dsmith@danplanet.com> wrote:

> Is there a more efficient way I can submit patches in the future, a lá
> github pull requests? I'm really struggling to construct the patches you
> desire using mercurial. I'm used to git's extensive history rewriting
> facilities. Can I submit a git diff instead of an hg export?

You can, but then I have to commit it and manually specify your username.

If you enable the mq extension in mercurial, you can "qimport" a
revision, change it, "qrefresh" it, and then "qfinish" it back into a
changeset. However, it's much easier if you never actually commit it and
just use "qnew" and "qrefresh" to edit it. It's quilt-like functionality
integrated into mercurial, which is really ideal for preparing patches
for upstream. It's so handy for that, I loathe using git for similar
operations.

> I've attached a patch with your suggested edits.

Applied, thanks very much for your work and patience!

--
Dan Smith
www.danplanet.com
KK7DS

_______________________________________________
chirp_devel mailing list
chirp_devel@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_devel