On Tue, Oct 18, 2016 at 04:25:48PM +0200, Tino Mettler wrote:
> How about a git branch "experimental" or similar?
FYI, I just pushed out the rtnl work. The log prefix stuff will have
to wait until I have a chance to try it out myself...
Thanks,
Richard
On Tue, 2016-10-18 at 08:38 +0200, Richard Cochran wrote:
> On Mon, Oct 17, 2016 at 08:39:16PM +, Keller, Jacob E wrote:
> >
> > Sounds good to me. I don't have any current issues, but being able
> > to
> > let people know that the RTNL link handling will be in 1.7 will be
> > nice. Thanks
On Tue, Oct 18, 2016 at 12:43:39PM +0200, Tino Mettler wrote:
> I'd like to test, but I don't see any commits since the 1.7 release,
> except for one commit from August. I'm
> using git://git.code.sf.net/p/linuxptp/code. Is this intended?
Yes, I don't push out anything unless the patches have
On Sun, 2016-10-16 at 13:09 +0200, Richard Cochran wrote:
> If you know of any other problems with 1.7 or in the current git
> head,
> please let me know right away.
Hi Richard,
I'd like to test, but I don't see any commits since the 1.7 release,
except for one commit from August. I'm
using
On Mon, Oct 17, 2016 at 08:39:16PM +, Keller, Jacob E wrote:
> Sounds good to me. I don't have any current issues, but being able to
> let people know that the RTNL link handling will be in 1.7 will be
> nice. Thanks for all your work.
Maybe rtnl is not quite ready yet. I'd like positive
On Sun, 2016-10-16 at 13:09 +0200, Richard Cochran wrote:
> Dear linuxptp users and developers,
>
> I am planning to release version 1.8 in one week, without any major
> new features, in order to fix the regression in version 1.7.
>
> [ Sound familiar? The same thing happened to 1.6. I don't
