From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ie0-x231.google.com (ie-in-x0231.1e100.net [IPv6:2607:f8b0:4001:c03::231]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 59FD621F1DA for ; Sun, 3 Feb 2013 22:06:31 -0800 (PST) Received: by mail-ie0-f177.google.com with SMTP id 16so5130287iea.8 for ; Sun, 03 Feb 2013 22:06:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=q5tThrgBylKu1ghLuq4c+/s/pt3M4k7D1xfS95PJkYQ=; b=ym3W+C8oLbd0tqFLtJ58vFwEjESogAbGzJYTE8XqqlyQjp4ou5WFJLh9rEtdOOaf4R otOiE/qSAwXJJzap5bouxmVjTTTOVZgEoDKMnue0kV8BEPOU/ghLB/ZzWP4Hq8vErNl+ Mcyea1TGBhyshZZR9P7cr8IygLnVM87jk4v9CuOeyBtq4ESdGdn8IWF0a8d1HM0mdnHt CzFBrGDJR4VNeG+tCQl56WN53tkKzC+akQNdQgDdKLcddz+rNRjIu4RL7R3Sf2BEvIGp Nf3Bxv+eB9GNbKWnrvr8ZJdEQzfrtq8O0A0QOxY3fN7KDoID5uv2cFsJI+ODD4LGbkRq VlrA== MIME-Version: 1.0 X-Received: by 10.43.62.12 with SMTP id wy12mr14531998icb.19.1359957990353; Sun, 03 Feb 2013 22:06:30 -0800 (PST) Received: by 10.64.135.39 with HTTP; Sun, 3 Feb 2013 22:06:30 -0800 (PST) In-Reply-To: References: <5108180E.4030602@gmail.com> <51094F04.7010602@gmail.com> <510AAD45.9060906@gmail.com> Date: Sun, 3 Feb 2013 22:06:30 -0800 Message-ID: From: Dave Taht To: Ketan Kulkarni Content-Type: multipart/alternative; boundary=bcaec51d2980ecab2604d4dfe428 Cc: cerowrt-devel Subject: Re: [Cerowrt-devel] administrative questions X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 06:06:31 -0000 --bcaec51d2980ecab2604d4dfe428 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable re: your bugs https://www.bufferbloat.net/issues/424 through 426. Thank you! Had I noticed I'd have tried to fold these into 3.7.5-2. in the case of emailing the bug tracker a new bug, it is better to attach the patch rather than put it inline. In the case of emailing humans, inline on this list is fine and will get you more eyeballs. Did these patches apply to 3.7.x? On Fri, Feb 1, 2013 at 7:51 AM, Ketan Kulkarni wrote: > Thanks William > Its generally Dave who decides and applies the patches. > Building cerowrt has been a pain for us (except Dave) for a while. > No, building cero is a PITA for me too! I did build a builder vm recently in the hope I could make it easier for people. Haven't had the bandwidth to upload 5GB... cut it down to 2GB... it's a zillion times slower than a native build... Not particularly well documented is that current development of cerowrt is in the cerowrt-next, cerofiles-next, and ceropackages-3.3 repos on github. I HAVE been pushing and tagging the more good releases in the hope that someone would try to update the build_cero.sh script to match the current reality. The website and onboard doc are in a dire need of a facelift... > On Jan 31, 2013 11:13 PM, "William Allen Simpson" < > william.allen.simpson@gmail.com> wrote: > >> On 1/30/13 10:03 PM, Ketan Kulkarni wrote: >> >>> Thanks William. Please try re-logging in and you should get the require= d >>> access. >>> >> >> OK, I've submitted a small patch series fixing a 0-day and a crashing bu= g. >> Is this the correct process? The lines don't display very well, but the >> emails sent look OK. >> >> Next time, I'll try {{{ }}} bracing to signal no text processing. That >> works on some other trackers. >> >> --=20 Dave T=E4ht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html --bcaec51d2980ecab2604d4dfe428 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable re: your bugs https://ww= w.bufferbloat.net/issues/424 through 426.

Thank you! Had I notic= ed I'd have tried to fold these into 3.7.5-2.

in the case of ema= iling the bug tracker a new bug, it is better to attach the patch rather th= an put it inline.

In the case of emailing humans, inline on this list is fine and will ge= t you more eyeballs.

Did these patches apply to 3.7.x?

On Fri, Feb 1, 2013 at 7:51 AM, Ketan Kulkarni <ketk= ulka@gmail.com> wrote:

Thanks William
Its generally Dave who decides and applies the patches.
Building cerowrt has been a pain for us (except Dave) for a while.


No, building cero is a PITA for me too!

I did buil= d a builder vm recently in the hope I could make it easier for people. Have= n't had the bandwidth to upload 5GB... cut it down to 2GB... it's a= zillion times slower than a native build...

Not particularly well documented is that current development of cerowrt= is in the cerowrt-next, cerofiles-next, and ceropackages-3.3 repos on gith= ub.

I HAVE been pushing and tagging the more good releases in the h= ope that someone would try to update the build_cero.sh script to match the = current reality. The website and onboard doc are in a dire need of a faceli= ft...


=A0
<= div class=3D"h5">
On Jan 31, 2013 11:13 PM, "William Allen Si= mpson" <william.allen.simpson@gmail.com> wrote:
On 1/30/13 10:03 PM, Ketan Kulkarni wrote:
Thanks William. Please try re-logging in and you should get the required ac= cess.

OK, I've submitted a small patch series fixing a 0-day and a crashing b= ug.
Is this the correct process? =A0The lines don't display very well, but = the
emails sent look OK.

Next time, I'll try {{{ }}} bracing to signal no text processing. =A0Th= at
works on some other trackers.




--
Dave T=E4ht=

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/= subscribe.html=20 --bcaec51d2980ecab2604d4dfe428--