[chirp_devel] [Patch][ft4] Tone and upload fixes #4787

[Dan Clemmensen]

>>* OK. I will start from what is in your current repository (i.e., the initial ft4.py) and make isolated incremental changes that cumulatively will reach my current working file.
*>*> Patches:
*>*> 1) whitespace, spelling, other non-code changes
*>*> 2) re-arrangement
*>


*> 3) through N): incremental fixups, each addressing a specific
issue.>This would be great thanks. So just to be clear you're doing
that for this patch or just in the future?*

Sigh. I guess I'd better start from the very first one: the "patch"
(i.e. the whole file) named add_ft4. You should therefore ignore my
most recent (i.e, only other) patch.

This will take awhile, so I may submit some intermediates one at a
time. If I get ambitious I will submit multiple patches in a set. So,
my proposed
methodology is to pull a completely fresh repository, then begin a
cycle of creating and soft-committing incremental patches, and then
producing the
multi-patch single submittal. Is it acceptable to continue to use
issue #4787 at least until I catch up?







On Mon, Feb 25, 2019 at 12:40 PM Dan Smith via chirp_devel <
chirp_devel at intrepid.danplanet.com> wrote:

> > That's fine. I was worried maybe it worked _only_ on py2. It's not a
> requirement to be working on py3 yet, so that's totally cool.
>
> Re-reading myself, I meant "only on py3" above :)
>
> --Dan
> _______________________________________________
> chirp_devel mailing list
> chirp_devel at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20190225/f26b0153/attachment-0001.html