Branch for gr-air-modes receiver and GNU Radio master (3.7) branch

GNU Radio
1

I’ve updated the gr-air-modes application to work with the latest GNU
Radio
master branch. This is the aircraft Mode S transponder receiver by Nick
Foster.

See branch ‘gnuradio-3.7’ on:

https://github.com/jmcorgan/gr-air-modes.git

As an example of the type of changes needed to go from 3.6 to 3.7 in a
GNU
Radio application, you can examine the last (and only) commit on the
branch:

https://github.com/jmcorgan/gr-air-modes/commit/ec1a7ac1

Note that these are almost entirely mechanical; none of the actual DSP
code
needed to change.

2

On 05/28/2013 09:42 AM, Johnathan C. wrote:

I’ve updated the gr-air-modes application to work with the latest GNU Radio
master branch. This is the aircraft Mode S transponder receiver by Nick
Foster.

See branch ‘gnuradio-3.7’ on:

https://github.com/jmcorgan/gr-air-modes.git

If I may be so bold, it may be better for your consumers (us lowly
people that use the software) if you were to make an actual release
tarball (call it 0.0.0.0.1 for all I care) with support for the released
version of gnuradio and let git track git gnu-radio. Normally I expect
to not need to randomly track git branches, I expect master to work
against master or assume the work hasn’t been done yet.

Just my 0.02$

Thanks,
Zero

3

On Tue, May 28, 2013 at 7:15 AM, Richard F. [email protected]
wrote:

If I may be so bold, it may be better for your consumers (us lowly
people that use the software) if you were to make an actual release
tarball (call it 0.0.0.0.1 for all I care) with support for the released
version of gnuradio and let git track git gnu-radio. Normally I expect
to not need to randomly track git branches, I expect master to work
against master or assume the work hasn’t been done yet.

I am sorry your expectations are not being met.

I’m not the maintainer of that software package; I merely created a
branch
to show the process of upgrading from 3.6 to 3.7 for a non-trivial
application, as a way to help GNU Radio application developers do it
with
their own software.

4

On 05/28/2013 10:48 AM, Johnathan C. wrote:

I am sorry your expectations are not being met.

Sorry, I didn’t mean to suggest anything negative about anyone doing
this work. I was merely trying to point out a problem I’m seeing and a
suggested usability improvement.

I’m not the maintainer of that software package; I merely created a branch
to show the process of upgrading from 3.6 to 3.7 for a non-trivial
application, as a way to help GNU Radio application developers do it with
their own software.

And that alone is most appreciated :slight_smile:

Thanks,
Zero