discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Feature Request


From: Tom Rondeau
Subject: Re: [Discuss-gnuradio] Feature Request
Date: Tue, 24 Mar 2015 10:00:16 -0700

On Tue, Mar 24, 2015 at 9:55 AM, Richard Bell <address@hidden> wrote:
Sebastian,

Now that the "issue" is on the issue tracker, how long does it usually take for that to make it into the distributed version of gnu radio? What has to happen before then? I'm curious.

v/r,
Rich

Rich,

We have two pages that address those questions. Easier than reproducing the answers here:

http://gnuradio.org/redmine/projects/gnuradio/wiki/Development#Dealing-with-the-GNU-Radio-Issue-Tracker

and

http://gnuradio.org/redmine/projects/gnuradio/wiki/Development#How-long-does-it-take-for-my-patch-to-become-part-of-GNU-Radio

And to add to that last link, also the available time from the developer how would be implementing that feature. So it'll depend on Sebastian queuing algorithm.

Tom

 
On Tue, Mar 24, 2015 at 8:02 AM, Koslowski, Sebastian (CEL) <address@hidden> wrote:

On 03/23/2015 05:43 PM, Richard Bell wrote:
> The second was a 'comment through' option. This comments out the block
> and passes data through it to the next block. Saves having to mess
> with wires between blocks that are commented out.

Martin's quite right, there is way more to be done, than there is time =)

In this case, however, I had the code pretty much done already for
another feature.
See http://gnuradio.org/redmine/issues/780

Sebastian


_______________________________________________
Discuss-gnuradio mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio



reply via email to

[Prev in Thread] Current Thread [Next in Thread]