From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/ceropackages] b4efe1: Mistyped url for ntp-dev
Date: Sat, 11 Feb 2012 07:58:06 -0800 [thread overview]
Message-ID: <4f36900e30cf6_6e141a4baf4963ca@sh2.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/ceropackages
Commit: b4efe1d07431a6f36013d35f1bc1b6b3a5bd590b
https://github.com/dtaht/ceropackages/commit/b4efe1d07431a6f36013d35f1bc1b6b3a5bd590b
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-02-11 (Sat, 11 Feb 2012)
Changed paths:
M net/ntpd/Makefile
Log Message:
-----------
Mistyped url for ntp-dev
Commit: 5376fa8fd3c122ab39cebbe0bd7edeb29e252cdb
https://github.com/dtaht/ceropackages/commit/5376fa8fd3c122ab39cebbe0bd7edeb29e252cdb
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-02-11 (Sat, 11 Feb 2012)
Changed paths:
M net/ntpd/Makefile
Log Message:
-----------
Enable dnsval and autokey in ntpd
Hopefully we're getting closer and closer to a working
dnssec-aware ntpd, which will close a ton of bugs.
I also have a longstanding, old ntp related crypto patch for time
for babeld to authenticate routes based on validly exchanging time...
Commit: e794c09ec948d449d37dcb56d45d3740783676c4
https://github.com/dtaht/ceropackages/commit/e794c09ec948d449d37dcb56d45d3740783676c4
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-02-11 (Sat, 11 Feb 2012)
Changed paths:
M net/ntpd/Makefile
Log Message:
-----------
Failed attempt at coaxing the latest ntp to build
it really wants threads.
It really wants to check if threads yield
Perhaps I'll try backporting the patch to the mainline version
Compare: https://github.com/dtaht/ceropackages/compare/f41993a...e794c09
reply other threads:[~2012-02-11 15:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4f36900e30cf6_6e141a4baf4963ca@sh2.rs.github.com.mail \
--to=noreply@github.com \
--cc=cerowrt-commits@lists.bufferbloat.net \
/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