On 05/28/2013 10:48 AM, Johnathan Corgan wrote: > On Tue, May 28, 2013 at 7:15 AM, Richard Farina <[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.
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 :-) Thanks, Zero _______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
