[chirp_devel] chirp_devel Digest, Vol 140, Issue 7
Mel Terechenok
Sat Dec 10 13:24:22 PST 2022
I can test the Wouxun KG-935G.
mrtjr1
Mel
On Sat, Dec 10, 2022, 3:00 PM <chirp_devel-request at intrepid.danplanet.com>
wrote:
> Send chirp_devel mailing list submissions to
> chirp_devel at intrepid.danplanet.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> or, via email, send a message with subject or body 'help' to
> chirp_devel-request at intrepid.danplanet.com
>
> You can reach the person managing the list at
> chirp_devel-owner at intrepid.danplanet.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of chirp_devel digest..."
>
>
> Today's Topics:
>
> 1. Re: Call for help (Matthew Poletiek)
> 2. Re: Call for help (Dan Smith)
> 3. Re: Call for help (Dave Allan)
> 4. Re: Call for help (Dan Smith)
> 5. Re: Call for help (Ran Katz)
> 6. Re: Call for help (Pavel Milanes Costa (CO7WT))
> 7. Re: Call for help (Jim Unroe)
> 8. Re: Call for help (Pavel Milanes Costa (CO7WT))
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 9 Dec 2022 16:09:03 -0600
> From: Matthew Poletiek <matthew.poletiek at gmail.com>
> Subject: Re: [chirp_devel] Call for help
> To: Jim Unroe <rock.unroe at gmail.com>
> Cc: chirp devel <chirp_devel at intrepid.danplanet.com>
> Message-ID:
> <
> CAJhSV8vzDCYE-xBJJAx27UuuN6_+p1ayabtrcd2xaqeyEe9KhA at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Awesome! Disregard then!
>
> On Fri, Dec 9, 2022, 11:17 Jim Unroe <rock.unroe at gmail.com> wrote:
>
> > Hi Matthew,
> >
> > On Fri, Dec 9, 2022 at 11:10 AM Matthew Poletiek via chirp_devel
> > <chirp_devel at intrepid.danplanet.com> wrote:
> > >
> > > HI Dan.
> > >
> > > I have a Baofeng_BF-F8HP. I might be able to find some time this
> weekend!
> > >
> >
> > Thank you for your willingness to help. Just so that you are aware,
> > all of the radios that are supported by the uv5r.py driver (which
> > includes the Baofeng BF-F8HP) have been tested.
> >
> > Jim KC9HI
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20221209/6a32e241/attachment-0001.html
>
> ------------------------------
>
> Message: 2
> Date: Fri, 9 Dec 2022 16:14:20 -0800
> From: Dan Smith <dsmith at danplanet.com>
> Subject: Re: [chirp_devel] Call for help
> To: chirp devel <chirp_devel at intrepid.danplanet.com>
> Message-ID: <AFB165FA-D246-4260-8F70-F883FA81219A at danplanet.com>
> Content-Type: text/plain; charset=us-ascii
>
> > That's cool, a VX-6 would be good to knock off the list, and I think
> it's likely to "just work" because it shares a lot in common with the other
> radios in that vintage (VX-7, VX-8, etc). That said, I haven't actually
> tested those since 2019, so I should re-do that just to be sure. I'll try
> to do that today, but will look forward to your report about the VX-6.
>
> I confirmed that my VX-7 and VX-8DR radios are still good, so I suspect
> your VX-6 will be no problem.
>
> Also, this morning I scraped some data out of our error reports and added
> a "Market Share" column to the testing matrix, which gives us an idea of
> which radios are the most important to get tested.
>
> https://github.com/kk7ds/chirp/blob/py3/tests/Python3_Driver_Testing.md
>
> Luckily, we've got all the major ones already, and even though only 53% of
> models have been tested as working, that represents 77% of the share of
> chirp users, which is pretty good. Interestingly, the VX-6 is oddly popular
> amongst its siblings:
>
> Yaesu_VX-3 0.08%
> Yaesu_VX-5 0.07%
> Yaesu_VX-6 0.16%
> Yaesu_VX-7 0.09%
> Yaesu_VX-8DR 0.03%
>
> Still tiny compared to the almighty UV-5R, but going strong compared to
> peers.
>
> I'm also thinking of marking all the Kenwood live radios as implied
> tested, as these are almost all the same code, and being string-based,
> pretty solid. That will increase our numbers a bit more. After the initial
> conversion, I've not encountered any problems with any of those that I've
> tried.
>
> I think starting to push users to the newer builds (especially if they're
> on platforms like Linux and MacOS that desperately need a modern platform)
> when 80% of them will be supported is pretty reasonable.
>
> --Dan
>
> ------------------------------
>
> Message: 3
> Date: Fri, 9 Dec 2022 22:00:41 -0500
> From: Dave Allan <danplanet at dpallan.com>
> Subject: Re: [chirp_devel] Call for help
> To: Dan Smith <dsmith at danplanet.com>,
> chirp_devel at intrepid.danplanet.com
> Message-ID: <Y5P2WbpK7s7gP3T/@dpallan.com>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> I have a Leixen VV-898, and I'll try to get to it this weekend.
>
> On Fri, Dec 09, 2022 at 07:45:28AM -0800, Dan Smith via chirp_devel wrote:
> >I haven't seen a lot of response to this (specifically the radio testing
> effort) this week. Jim has been plugging away at testing what he has in his
> museum of radios and is making us all look bad (in a good way). But,
> there's a lot of stuff on the list that he doesn't have in his collection,
> and I've exhausted mine.
> >
> >I know David spoke up that he might be able to do some testing, but other
> than that I'm thinking we might need to rope in a larger audience.
> >
> >If you think you have radios on the list that you can test locally:
> >
> >https://github.com/kk7ds/chirp/blob/py3/tests/Python3_Driver_Testing.md
> >
> >Please speak up, even if you won't be able to do it right away. Knowing
> who has (or has access) to what at least gives an idea of how much more
> we're likely to be able to do.
> >
> >If I haven't heard much by Monday I think I'll try to send out a similar
> call for help to the users list and various other places in hopes that some
> capable user types can help close that gap. That's a potential large can of
> worms though. I think almost all the Icom models are likely to "just work",
> and a bunch of the Yaesu ones will as well. However, many of the others
> will require work I think.
> >
> >Thanks!
> >
> >--Dan
> >
> >> On Dec 4, 2022, at 08:58, Dan Smith via chirp_devel <
> chirp_devel at intrepid.danplanet.com> wrote:
> >>
> >> Hi all,
> >>
> >> In case you haven't been seeing the activity lately, much progress is
> being made on the py3 branch in github:
> >>
> >> https://github.com/kk7ds/chirp/commits/py3
> >>
> >> Thanks to a lot of help from @sv1 and @KC9HI, all of the drivers are
> now at least syntax-compatible with python3, running automated tests, and
> progress is being made to test (with real hardware) as many as possible to
> iron out remaining incompatibilities:
> >>
> >> https://github.com/kk7ds/chirp/blob/py3/tests/Python3_Driver_Testing.md
> >>
> >> As of today, about 38% have been tested, so we've got some work to do.
> I think it's unrealistic to get all of them tested in the short term, but
> we should at least shoot for the major brands and popular models as much as
> possible. So, the first call for help item is:
> >>
> >> 1. If you have a radio in that list not marked as tested, please test
> and record it in tests/py3_driver_testers.txt with a PR
> >>
> >> At the end of this email is a list of radios we have leads on for
> testing. Feel free to claim one of those, but the real prizes are the major
> models not on that list.
> >>
> >> Next up is UI parity. I've been doing a lot of work on the wx UI lately
> and I'm pretty happy with it, so much that I've been using it exclusively
> for my personal programming for a while now. There are still some gaps
> missing that I need to take care of, and my current todo list is wrapped up
> here:
> >>
> >> https://chirp.danplanet.com/versions/21
> >>
> >> There are some things I'm not planning to pull into the new UI at all,
> and some things that can come later. So, the second call for help item is:
> >>
> >> 2. Please test the new UI, help brainstorm what needs to be implemented
> (or fixed) before we start looking for more regular users to start using it
> >>
> >> I've got one-off test builds here:
> >>
> >> https://trac.chirp.danplanet.com/chirp_next/
> >>
> >> and will continue to generate those regularly until we get to the point
> of doing them automatically. The new macos build is much better than it has
> ever been, IMHO. It feels very native and will have universal2 intel/arm
> support the next time I roll it. Testing the bundled builds is important
> for sure, but getting a development environment running is also easier. You
> pretty much just need a recent python3 (3.10 recommended) and:
> >>
> >> $ pip install -r requirements.txt
> >>
> >> ...should get you there. Please file issues for things you find, and
> select "chirp-py3" for "target version" and "chirp version" to help keep
> track of bugs only in the py3 version.
> >>
> >> I've been keeping the py3 branch in sync with changes to master for
> several months and even though it's doable, it's majorly not fun. I think
> the light is visible at the end of the tunnel at this point, so I'd really
> like to make 2023 the year we freeze work on the current py2 branch and get
> people moving to the new stuff. I'd like to be able to start getting "power
> users" testing the new builds early next year, which hopefully will help
> fill out the model testing edges.
> >>
> >> Thoughts on the plan?
> >>
> >> If you've got a radio on the list that needs testing, please speak up
> here so we at least know which ones are potentially testable.
> >>
> >> Thanks!
> >>
> >> --Dan
> >>
> >> List of drivers for which there is known likely tester already:
> >>
> >> Abbree_AR-518 iradio_uv_5118.py
> >> AnyTone_OBLTR-8R anytone_ht.py
> >> AnyTone_TERMN-8R anytone_ht.py
> >> BTECH_GMRS-V1 gmrsvu1.py
> >> BTECH_GMRS-V2 gmrsv2.py
> >> BTECH_MURS-V1 mursv1.py
> >> BTECH_UV-50X3 vgc.py
> >> BTECH_UV-5X3 uv5x3.py
> >> Baofeng_BF-T1 bf-t1.py
> >> Baofeng_UV-6R uv6r.py
> >> Explorer_QRZ-1 th_uv88.py
> >> LUITON_LT-316 retevis_rt22.py
> >> LUITON_LT-580_UHF th9000.py
> >> LUITON_LT-580_VHF th9000.py
> >> LUITON_LT-725UV lt725UV.py
> >> MTC_UV-5R-3 uv5x3.py
> >> Radioddity_GA-2S h777.py
> >> Radioddity_R2 radioddity_r2.py
> >> Retevis_H777_Plus h777.py
> >> Retevis_RB15 retevis_rb15.py
> >> Retevis_RB17P retevis_rb17p.py
> >> Retevis_RB615 retevis_rb15.py
> >> Retevis_RT1 retevis_rt1.py
> >> Retevis_RT22 retevis_rt22.py
> >> Retevis_RT22FRS retevis_rt22.py
> >> Retevis_RT23 retevis_rt23.py
> >> Retevis_RT26 retevis_rt26.py
> >> Retevis_RT6 baofeng_wp970i.py
> >> Retevis_RT622 retevis_rt22.py
> >> Retevis_RT76P retevis_rt76p.py
> >> Retevis_RT85 th_uv88.py
> >> Retevis_RT87 retevis_rt87.py
> >> Retevis_RT9000D_136-174 th9000.py
> >> Retevis_RT9000D_136-174 th9000.py
> >> Retevis_RT9000D_136-174 th9000.py
> >> Retevis_RT98 retevis_rt98.py
> >> Rugges_RH5R-V2 rh5r_v2.py
> >> TDXone_TD-Q8A tdxone_tdq8a.py
> >> TID_TD-M8 retevis_rt22.py
> >> TYT_TH-UV88 th_uv88.py
> >> TYT_TH9000_144 th9000.py
> >> TYT_TH9000_220 th9000.py
> >> TYT_TH9000_440 th9000.py
> >> WLN_KD-C1 retevis_rt22.py
> >> Wouxun_KG-UV6 wouxun.py
> >> Yaesu_FT70D ft70.py
> >> Yaesu_FTM350 ftm350.py
> >> Zastone_ZT-X6 retevis_rt22.py
> >> _______________________________________________
> >> 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
> >
> >_______________________________________________
> >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
> >
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 9 Dec 2022 19:14:11 -0800
> From: Dan Smith <dsmith at danplanet.com>
> Subject: Re: [chirp_devel] Call for help
> To: chirp devel <chirp_devel at intrepid.danplanet.com>
> Message-ID: <2055508C-F069-4931-838B-B4F22B69B208 at danplanet.com>
> Content-Type: text/plain; charset=us-ascii
>
> > I have a Leixen VV-898, and I'll try to get to it this weekend.
>
> Great, thanks! I just took a look and that driver and it will definitely
> need some love to make it happy, but it seems quite simple and thus should
> be fairly straightforward. There are lots of recent examples of conversions
> in the tree to look at. Here are a few:
>
>
> https://github.com/kk7ds/chirp/commits/fda922775d6f69e8d8f5b93f0f95888b1d7c4f1e
>
>
> https://github.com/kk7ds/chirp/commit/adb317bb0db923210ef7253525a6decac8bf7bf3
>
>
> https://github.com/kk7ds/chirp/commit/4c70adca96328acabacd8f4d9a77f464d6b7b248
>
> --Dan
>
> ------------------------------
>
> Message: 5
> Date: Sat, 10 Dec 2022 19:23:47 +0200
> From: Ran Katz <rankatz at gmail.com>
> Subject: Re: [chirp_devel] Call for help
> To: Dan Smith <dsmith at danplanet.com>,
> chirp_devel at intrepid.danplanet.com
> Message-ID: <35F7C2B0-31F4-4A01-BC25-25553ADAD5AB at gmail.com>
> Content-Type: text/plain; charset=utf-8
>
> I?ll test the Quansheng tg-uv2, hopefully this week
>
> Ran
>
> > On 9 Dec 2022, at 18:13, Dan Smith via chirp_devel <
> chirp_devel at intrepid.danplanet.com> wrote:
> >
> > ?
> >>
> >> I have a Baofeng_BF-F8HP. I might be able to find some time this
> weekend!
> >
> > Sweet, not on the list nor in Jim's museum, that'll be a good one :)
> >
> > Thanks!
> >
> > --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
>
>
> ------------------------------
>
> Message: 6
> Date: Sat, 10 Dec 2022 13:35:31 -0500
> From: "Pavel Milanes Costa (CO7WT)" <pavelmc at gmail.com>
> Subject: Re: [chirp_devel] Call for help
> To: chirp_devel at intrepid.danplanet.com
> Message-ID: <ff3a00cd-7dee-8556-b8b2-d162f32a9f0b at gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi, to all
>
> Not much free time on this side, but catching up.
>
> Radios at hand that I will check and the family that will cover:
>
> * Feidaxin FD-268A: all supported Feidaxin listed
> * Baofeng BF-T1
> * Vertex Standard FTL-1011 & 2011: all supported Vertex Standard FTL-****
>
> Also posted a request for help on the local ham group for the Kenwoods
> 260 family, That's a very common radio family here, once tested that
> will clear all this models:
>
> * TK-260, TK-270, TK-272, TK-278, TK-360, TK-370, TK-372 & TK-378
>
> Will let you now!
>
> 73 Pavel CO7WT.
>
> El 4/12/22 a las 11:58, Dan Smith via chirp_devel escribi?:
> > Hi all,
> >
> > In case you haven't been seeing the activity lately, much progress is
> being made on the py3 branch in github:
> >
> > https://github.com/kk7ds/chirp/commits/py3
> >
> > Thanks to a lot of help from @sv1 and @KC9HI, all of the drivers are now
> at least syntax-compatible with python3, running automated tests, and
> progress is being made to test (with real hardware) as many as possible to
> iron out remaining incompatibilities:
> >
> > https://github.com/kk7ds/chirp/blob/py3/tests/Python3_Driver_Testing.md
> >
> > As of today, about 38% have been tested, so we've got some work to do. I
> think it's unrealistic to get all of them tested in the short term, but we
> should at least shoot for the major brands and popular models as much as
> possible. So, the first call for help item is:
> >
> > 1. If you have a radio in that list not marked as tested, please test
> and record it in tests/py3_driver_testers.txt with a PR
> >
> > At the end of this email is a list of radios we have leads on for
> testing. Feel free to claim one of those, but the real prizes are the major
> models not on that list.
> >
> > Next up is UI parity. I've been doing a lot of work on the wx UI lately
> and I'm pretty happy with it, so much that I've been using it exclusively
> for my personal programming for a while now. There are still some gaps
> missing that I need to take care of, and my current todo list is wrapped up
> here:
> >
> > https://chirp.danplanet.com/versions/21
> >
> > There are some things I'm not planning to pull into the new UI at all,
> and some things that can come later. So, the second call for help item is:
> >
> > 2. Please test the new UI, help brainstorm what needs to be implemented
> (or fixed) before we start looking for more regular users to start using it
> >
> > I've got one-off test builds here:
> >
> > https://trac.chirp.danplanet.com/chirp_next/
> >
> > and will continue to generate those regularly until we get to the point
> of doing them automatically. The new macos build is much better than it has
> ever been, IMHO. It feels very native and will have universal2 intel/arm
> support the next time I roll it. Testing the bundled builds is important
> for sure, but getting a development environment running is also easier. You
> pretty much just need a recent python3 (3.10 recommended) and:
> >
> > $ pip install -r requirements.txt
> >
> > ...should get you there. Please file issues for things you find, and
> select "chirp-py3" for "target version" and "chirp version" to help keep
> track of bugs only in the py3 version.
> >
> > I've been keeping the py3 branch in sync with changes to master for
> several months and even though it's doable, it's majorly not fun. I think
> the light is visible at the end of the tunnel at this point, so I'd really
> like to make 2023 the year we freeze work on the current py2 branch and get
> people moving to the new stuff. I'd like to be able to start getting "power
> users" testing the new builds early next year, which hopefully will help
> fill out the model testing edges.
> >
> > Thoughts on the plan?
> >
> > If you've got a radio on the list that needs testing, please speak up
> here so we at least know which ones are potentially testable.
> >
> > Thanks!
> >
> > --Dan
> >
> > List of drivers for which there is known likely tester already:
> >
> > Abbree_AR-518 iradio_uv_5118.py
> > AnyTone_OBLTR-8R anytone_ht.py
> > AnyTone_TERMN-8R anytone_ht.py
> > BTECH_GMRS-V1 gmrsvu1.py
> > BTECH_GMRS-V2 gmrsv2.py
> > BTECH_MURS-V1 mursv1.py
> > BTECH_UV-50X3 vgc.py
> > BTECH_UV-5X3 uv5x3.py
> > Baofeng_BF-T1 bf-t1.py
> > Baofeng_UV-6R uv6r.py
> > Explorer_QRZ-1 th_uv88.py
> > LUITON_LT-316 retevis_rt22.py
> > LUITON_LT-580_UHF th9000.py
> > LUITON_LT-580_VHF th9000.py
> > LUITON_LT-725UV lt725UV.py
> > MTC_UV-5R-3 uv5x3.py
> > Radioddity_GA-2S h777.py
> > Radioddity_R2 radioddity_r2.py
> > Retevis_H777_Plus h777.py
> > Retevis_RB15 retevis_rb15.py
> > Retevis_RB17P retevis_rb17p.py
> > Retevis_RB615 retevis_rb15.py
> > Retevis_RT1 retevis_rt1.py
> > Retevis_RT22 retevis_rt22.py
> > Retevis_RT22FRS retevis_rt22.py
> > Retevis_RT23 retevis_rt23.py
> > Retevis_RT26 retevis_rt26.py
> > Retevis_RT6 baofeng_wp970i.py
> > Retevis_RT622 retevis_rt22.py
> > Retevis_RT76P retevis_rt76p.py
> > Retevis_RT85 th_uv88.py
> > Retevis_RT87 retevis_rt87.py
> > Retevis_RT9000D_136-174 th9000.py
> > Retevis_RT9000D_136-174 th9000.py
> > Retevis_RT9000D_136-174 th9000.py
> > Retevis_RT98 retevis_rt98.py
> > Rugges_RH5R-V2 rh5r_v2.py
> > TDXone_TD-Q8A tdxone_tdq8a.py
> > TID_TD-M8 retevis_rt22.py
> > TYT_TH-UV88 th_uv88.py
> > TYT_TH9000_144 th9000.py
> > TYT_TH9000_220 th9000.py
> > TYT_TH9000_440 th9000.py
> > WLN_KD-C1 retevis_rt22.py
> > Wouxun_KG-UV6 wouxun.py
> > Yaesu_FT70D ft70.py
> > Yaesu_FTM350 ftm350.py
> > Zastone_ZT-X6 retevis_rt22.py
> > _______________________________________________
> > 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/20221210/ef998477/attachment-0001.html
>
> ------------------------------
>
> Message: 7
> Date: Sat, 10 Dec 2022 14:39:28 -0500
> From: Jim Unroe <rock.unroe at gmail.com>
> Subject: Re: [chirp_devel] Call for help
> To: "Pavel Milanes Costa (CO7WT)" <pavelmc at gmail.com>,
> chirp_devel at intrepid.danplanet.com
> Message-ID:
> <CADnO8U6W71KhB2FgfcY71gjc664TUsgyCRSSkB7KVvWGf8=
> dcA at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Hi Pavel,
>
> > Not much free time on this side, but catching up.
> >
> > Radios at hand that I will check and the family that will cover:
> >
> > Feidaxin FD-268A: all supported Feidaxin listed
> > Baofeng BF-T1
> > Vertex Standard FTL-1011 & 2011: all supported Vertex Standard FTL-****
>
> I happen to have a BF-T1 here. Since you have limited time available,
> I can go ahead and do that one if it is OK with you?
>
> Jim KC9HI
>
>
> ------------------------------
>
> Message: 8
> Date: Sat, 10 Dec 2022 14:43:35 -0500
> From: "Pavel Milanes Costa (CO7WT)" <pavelmc at gmail.com>
> Subject: Re: [chirp_devel] Call for help
> To: Jim Unroe <rock.unroe at gmail.com>,
> chirp_devel at intrepid.danplanet.com
> Message-ID: <552a7e95-c88a-a707-094f-e8081cfa6aa9 at gmail.com>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> Hi Jim
>
> Go ahead!
>
> I have to pick up the radios at my old house (the entire shack is in
> storage boxes, radios, tools, interfaces, etc) so you will make it
> faster than me.
>
> Cheers, Pavel.
>
> El 10/12/22 a las 14:39, Jim Unroe escribi?:
> > Hi Pavel,
> >
> >> Not much free time on this side, but catching up.
> >>
> >> Radios at hand that I will check and the family that will cover:
> >>
> >> Feidaxin FD-268A: all supported Feidaxin listed
> >> Baofeng BF-T1
> >> Vertex Standard FTL-1011 & 2011: all supported Vertex Standard FTL-****
> > I happen to have a BF-T1 here. Since you have limited time available,
> > I can go ahead and do that one if it is OK with you?
> >
> > Jim KC9HI
>
>
> ------------------------------
>
> _______________________________________________
> chirp_devel mailing list
> chirp_devel at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
>
>
> End of chirp_devel Digest, Vol 140, Issue 7
> *******************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20221210/e4736fe1/attachment-0001.html
More information about the chirp_devel
mailing list