From: Dave Taht <dave.taht@gmail.com>
To: "Török Edwin" <edwin+ml-cerowrt@etorok.net>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] A stable cerowrt release in sight
Date: Fri, 16 May 2014 13:54:53 -0700 [thread overview]
Message-ID: <CAA93jw6Sfpo=ggLHg4khg1RcNdG-nf719cD7FQHo71EP56cfhA@mail.gmail.com> (raw)
In-Reply-To: <53766E2B.3090507@etorok.net>
I think it finished compiling at 1AM, and I have been busy all day. Might work.
I also finished an archer test compile, which of course, failed to
boot entirely. I am taking saturday off... I will try to flash
3.10.40-4 on a 3800 before this evening, otherwise sunday.
On Fri, May 16, 2014 at 12:59 PM, Török Edwin
<edwin+ml-cerowrt@etorok.net> wrote:
> On 05/16/2014 09:36 AM, Dave Taht wrote:
>> it is now mid-may, about 3 months after I'd hoped to finally have a
>> stable release.
> [...]
>>
>> So hopefully the upcoming 3.10.40-4 build will be stable enough to
>> freeze on. If there is anything else that people want done before
>> freezing, let me know soonest.
>>
>
> Excellent news!
> So if I want to upgrade my router this weekend is 3.10.40-4
> ready for testing yet, or should I wait a bit more?
>
> Best regards,
> --Edwin
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
next prev parent reply other threads:[~2014-05-16 20:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 6:36 Dave Taht
2014-05-16 19:59 ` Török Edwin
2014-05-16 20:54 ` Dave Taht [this message]
2014-05-17 6:54 ` Valdis.Kletnieks
2014-05-18 1:15 ` Aristar
2014-05-18 13:48 ` Valdis.Kletnieks
2014-05-18 15:29 ` Dave Taht
2014-05-19 7:30 ` Maciej Soltysiak
2014-05-19 9:57 ` Sebastian Moeller
2014-05-19 16:29 ` Dave Taht
2014-05-19 17:49 ` Sebastian Moeller
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6Sfpo=ggLHg4khg1RcNdG-nf719cD7FQHo71EP56cfhA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=edwin+ml-cerowrt@etorok.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