From: Mark Constable <markc@renta.net>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] understanding_cerowrt_buildsystem
Date: Thu, 20 Sep 2012 23:05:39 +1000 [thread overview]
Message-ID: <505B14A3.6050302@renta.net> (raw)
In-Reply-To: <CAMZR1YC5D5oAGCKJQkzYBiXqNH4or6d8uxB2P9fLTLD+YsmTAg@mail.gmail.com>
On 09/20/12 20:41, Maciej Soltysiak wrote:
> Also it makes it harder for Dave to delegate building to somebody else
> as he hinted last time. Could at least we make a list on the wiki of
> most common build problems and questions?
Wouldn't it be better to use the issue tracker and pull requests at Github?
The whole point of Github is to make is easier for folks to cooperate and
accelerate project development and it has excellent tools for doing exactly
that, as long as the direction of the project allows for it and takes
advantage of the available social facilities.
I'd like to get more involved too but it just seems all too hard atm so I
build stock AA OpenWrt uml images instead, for now, hoping I can get up to
speed with understanding the CeroWrt build process.
next prev parent reply other threads:[~2012-09-20 13:05 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 [this message]
2012-09-21 15:35 ` Dave Taht
2012-09-21 17:04 ` Mark Constable
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=505B14A3.6050302@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