Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] radvd: bump to version 1.12
Date: Thu, 05 Jun 2014 15:18:41 -0300	[thread overview]
Message-ID: <5390B481.7070008@zacarias.com.ar> (raw)
In-Reply-To: <1401968249-32408-1-git-send-email-gustavo@zacarias.com.ar>

On 06/05/2014 08:37 AM, Gustavo Zacarias wrote:

> -RADVD_VERSION = 1.10.0
> +RADVD_VERSION = 1.12

Sigh, seems upstream skipped the 1.11 release, shipped as 1.12, then
noticed the skipping and renamed to 1.11 (or so, i haven't compared).
The announcement:
http://lists.litech.org/pipermail/radvd-devel-l/2014-June/000775.html
Website now says 1.11 is latest and 1.12 is no longer available.
So disregard and better wait until their mind is made up.
Thanks to Waldemar for bringing this up on irc.
Regards.

  reply	other threads:[~2014-06-05 18:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05 11:37 [Buildroot] [PATCH] radvd: bump to version 1.12 Gustavo Zacarias
2014-06-05 18:18 ` Gustavo Zacarias [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-06-10 17:58 Gustavo Zacarias
2014-06-11 12:29 ` Peter Korsgaard

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=5390B481.7070008@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.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