Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Mark Constable <markc@renta.net>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] understanding_cerowrt_buildsystem
Date: Sat, 22 Sep 2012 03:04:16 +1000	[thread overview]
Message-ID: <505C9E10.4020902@renta.net> (raw)
In-Reply-To: <CAA93jw6t1XSiFdNgXc9_dMq7Bq5vJQdUFJdVBcQ3LrVW1XdShw@mail.gmail.com>

On 09/22/12 01:35, Dave Taht wrote:
> Yes, getting cero (and openwrt) built right the first time is hard!

As mentioned in a previous message, having an obvious "canonical"
meta repo would give the rest of us something to focus on. If I go
to https://github.com/dtaht it's not obvious where to start unless
I (or misc newbie) click around on the various cerowrt* projects or
go off site via googling for further directions.

Bufferbloat is an academic ideal whereas cerowrt is the actual
implementation that is of most interest to me, so I can eventually
get a handle on the deeper understanding of all the neat tools and
concepts (hands on first, rtfm later). As a newbie, something like
https://github.com/cerowrt and a https://github.com/cerowrt/build
project would make for the most intuitive starting points but just
https://github.com/dtaht/cerowrt would be the next most obvious...
even if it's only a documentation project with a single README.md

> Regardless pls send along your github ids, and I'll add you.

markc -> https://github.com/markc


  reply	other threads:[~2012-09-21 17:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20  7:10 Oliver Niesner
2012-09-20 10:41 ` Maciej Soltysiak
2012-09-20 13:05   ` Mark Constable
2012-09-21 15:35     ` Dave Taht
2012-09-21 17:04       ` Mark Constable [this message]
2012-09-21 21:08       ` Maciej Soltysiak
2012-09-21 21:22         ` Dave Taht
2012-09-21 22:16 ` Dave Taht
2012-09-22  2:32   ` Outback Dingo

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=505C9E10.4020902@renta.net \
    --to=markc@renta.net \
    --cc=cerowrt-devel@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