From: Joe MacDonald <joe@deserted.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [OE-devel] [PATCH] ntp: Resolve some abnormal behaviors
Date: Fri, 14 Mar 2014 08:37:09 -0400 [thread overview]
Message-ID: <20140314123706.GA3469@deserted.net> (raw)
In-Reply-To: <6B3DF93B-C645-42A0-A36E-4EE3923E3905@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1669 bytes --]
[Re: [oe] [OE-devel] [PATCH] ntp: Resolve some abnormal behaviors] On 14.03.01 (Sat 14:57) Khem Raj wrote:
>
> On Mar 1, 2014, at 2:48 PM, Paul Eggleton <paul.eggleton@linux.intel.com> wrote:
>
> > On Saturday 01 March 2014 20:18:44 Burton, Ross wrote:
> >> On 1 March 2014 09:59, Paul Eggleton <paul.eggleton@linux.intel.com> wrote:
> >>> That would be nice, but since you can't actually distribute a product that
> >>> connects to the main pool.ntp.org server (you need to register your own
> >>> NTP
> >>> pool [1]) we've elected not to set any default so that you are encouraged
> >>> to do the right thing and explicitly set your own.
> >>
> >> We should probably put this in the documentation. I'll file a bug.
> >
> > Whose documentation though? ntp is part of meta-networking rather than OE-
> > Core.
> >
>
> README for meta-networking is best place.
I agree. I'm working through my backlog of merges right now but I've
not seen a readme patch. If I missed it, please let me know, otherwise
when I get a chance I'll propose a readme documenting this myself.
-J.
>
> > Cheers,
> > Paul
> >
> > --
> >
> > Paul Eggleton
> > Intel Open Source Technology Centre
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2014-03-14 12:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 6:18 [OE-devel] [PATCH] ntp: Resolve some abnormal behaviors Xufeng Zhang
2013-05-31 8:34 ` Paul Eggleton
2013-05-31 9:08 ` Xufeng Zhang
2013-05-31 9:14 ` Xufeng Zhang
2013-05-31 11:14 ` Paul Eggleton
2013-06-10 15:29 ` Joe MacDonald
2014-02-28 7:41 ` Xufeng Zhang
2014-03-01 4:33 ` Stephen Arnold
2014-03-01 9:59 ` Paul Eggleton
2014-03-01 20:18 ` Burton, Ross
2014-03-01 22:48 ` Paul Eggleton
2014-03-01 22:57 ` Khem Raj
2014-03-14 12:37 ` Joe MacDonald [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140314123706.GA3469@deserted.net \
--to=joe@deserted.net \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox