Glad to hear it! Thanks for making an awesome piece of software. CHIRP has totally changed how I use my HT. Happy to be of use contributing new memory maps.<br><br><div class="gmail_quote">On Wed, Jul 18, 2012 at 7:50 PM, Dan Smith <span dir="ltr"><<a href="mailto:dsmith@danplanet.com" target="_blank">dsmith@danplanet.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">> Is there a more efficient way I can submit patches in the future, a lá<br>
> github pull requests? I'm really struggling to construct the patches you<br>
> desire using mercurial. I'm used to git's extensive history rewriting<br>
> facilities. Can I submit a git diff instead of an hg export?<br>
<br>
</div>You can, but then I have to commit it and manually specify your username.<br>
<br>
If you enable the mq extension in mercurial, you can "qimport" a<br>
revision, change it, "qrefresh" it, and then "qfinish" it back into a<br>
changeset. However, it's much easier if you never actually commit it and<br>
just use "qnew" and "qrefresh" to edit it. It's quilt-like functionality<br>
integrated into mercurial, which is really ideal for preparing patches<br>
for upstream. It's so handy for that, I loathe using git for similar<br>
operations.<br>
<div class="im"><br>
> I've attached a patch with your suggested edits.<br>
<br>
</div>Applied, thanks very much for your work and patience!<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
Dan Smith<br>
<a href="http://www.danplanet.com" target="_blank">www.danplanet.com</a><br>
KK7DS<br>
<br>
</div></div><br>_______________________________________________<br>
chirp_devel mailing list<br>
<a href="mailto:chirp_devel@intrepid.danplanet.com">chirp_devel@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_devel" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_devel</a><br>
<br></blockquote></div><br>