From: Maciej Soltysiak <maciej@soltysiak.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] understanding_cerowrt_buildsystem
Date: Fri, 21 Sep 2012 23:08:41 +0200 [thread overview]
Message-ID: <CAMZR1YCoSN0dUM1UAV5CKyuU-6XNePFtcDjxvozNccR7s60KXw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6t1XSiFdNgXc9_dMq7Bq5vJQdUFJdVBcQ3LrVW1XdShw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]
On Fri, Sep 21, 2012 at 5:35 PM, Dave Taht <dave.taht@gmail.com> wrote:
> My overall thought at the moment is to hold a "building
> openwrt/cerowrt google hangout" with as many participants as possible,
> get some your versions built, record the thing, see what barriers
> there are to making it easier, and smash them.
>
Sounds good! I don't know all the time zones people are in, but I'm in CEST
(GMT+2 at the moment).
> I'm back in california now and migrating back to PDT, when would be a
> good time to get everyone together? Saturday?
>
Short notice, but might be. I suggest you invite folks, see how many join,
how many reject but wanted to join.
And hold another session a week after.
For the agenda I'd suggest including these topics:
- quick walkthrough of build process
- resolving missing file issue
- adding new software to packages
- any advice on kernel config?
I note that I'm very free with commit access to the ceropackages repo
> in particular. If, in order to make forward progress on the dlna, upnp
> issues, we have to move those into ceropackages, go for it. The whole
> point of ceropackages was to try to find ways to quickly spin up and
> eventually push out, new, improved, interesting packages into openwrt
> mainline.
>
> Regardless pls send along your github ids, and I'll add you.
>
Although I've done my share of coding, patching, using cvs, I'm a github
newbe:
https://github.com/pysiak
Regards,
Maciej
[-- Attachment #2: Type: text/html, Size: 2260 bytes --]
next prev parent reply other threads:[~2012-09-21 21:08 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
2012-09-21 21:08 ` Maciej Soltysiak [this message]
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=CAMZR1YCoSN0dUM1UAV5CKyuU-6XNePFtcDjxvozNccR7s60KXw@mail.gmail.com \
--to=maciej@soltysiak.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.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