From: Maciej Soltysiak <maciej@soltysiak.com>
To: GitHub <noreply@github.com>
Cc: cerowrt-commits@lists.bufferbloat.net
Subject: Re: [dtaht/ceropackages-3.10] a8699d: libsodium: add libsodium, a p(ortable|ackageable) ...
Date: Mon, 14 Apr 2014 09:47:24 +0200 [thread overview]
Message-ID: <CAMZR1YAps8n7grNdqvvZJ=Q49hmE2cnGZKX=J1s422qdKqv_VQ@mail.gmail.com> (raw)
In-Reply-To: <534ac8f7e7470_1b479e9d3c81676@hookshot-fe1-cp1-prd.iad.github.net.mail>
Thanks Dave!
On Sun, Apr 13, 2014 at 7:27 PM, GitHub <noreply@github.com> wrote:
> Branch: refs/heads/master
> Home: https://github.com/dtaht/ceropackages-3.10
> Commit: a8699d353e35f67bdbfdd6f41d0e18012d7db133
> https://github.com/dtaht/ceropackages-3.10/commit/a8699d353e35f67bdbfdd6f41d0e18012d7db133
> Author: Stephen Walker <stephendwalker+github@gmail.com>
> Date: 2014-04-13 (Sun, 13 Apr 2014)
>
> Changed paths:
> A libs/libsodium/Makefile
> A libs/libsodium/patches/001-fixfor-openwrt.patch
>
> Log Message:
> -----------
> libsodium: add libsodium, a p(ortable|ackageable) NaCl-based crypto library
>
>
> Commit: 8a38156aba67777eec194fba37ccf1a0ff356685
> https://github.com/dtaht/ceropackages-3.10/commit/8a38156aba67777eec194fba37ccf1a0ff356685
> Author: Stephen Walker <stephendwalker+github@gmail.com>
> Date: 2014-04-13 (Sun, 13 Apr 2014)
>
> Changed paths:
> M net/dnscrypt/Makefile
> R net/dnscrypt/patches/001-fixfor-openwrt.patch
>
> Log Message:
> -----------
> dnscrypt: update to 1.3.3
>
>
> Compare: https://github.com/dtaht/ceropackages-3.10/compare/24461e19e901...8a38156aba67
> _______________________________________________
> Cerowrt-commits mailing list
> Cerowrt-commits@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-commits
>
prev parent reply other threads:[~2014-04-14 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-13 17:27 GitHub
2014-04-14 7:47 ` Maciej Soltysiak [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='CAMZR1YAps8n7grNdqvvZJ=Q49hmE2cnGZKX=J1s422qdKqv_VQ@mail.gmail.com' \
--to=maciej@soltysiak.com \
--cc=cerowrt-commits@lists.bufferbloat.net \
--cc=noreply@github.com \
/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