From: Samuel Robb <sam@oneparticularharbor.net>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: Shaz <shazalive@gmail.com>,
linux-embedded <linux-embedded@vger.kernel.org>,
Security Engineering Archive <groupsecurityengineering@gmail.com>
Subject: Re: Useful IRC channels
Date: Wed, 23 Jul 2008 10:59:35 -0400 [thread overview]
Message-ID: <1216825175.12161.18.camel@samuelr.hq.netapp.com> (raw)
In-Reply-To: <20080723110755.GI4319@pengutronix.de>
On Wed, 2008-07-23 at 13:07 +0200, Robert Schwebel wrote:
> On Wed, Jul 23, 2008 at 03:41:23PM +0500, Shaz wrote:
> > Can anyone indicate some useful and active IRC channels on embedded
> > Linux and cross compilations? I need to sort out some tit bits, which
> > are not feasible and relevant for this list in some way :)
>
> #ptxdist on freenode.net
>
> rsc
Also #edev on freenode.net
-Samrobb
next prev parent reply other threads:[~2008-07-23 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 10:41 Useful IRC channels Shaz
2008-07-23 11:07 ` Robert Schwebel
2008-07-23 14:59 ` Samuel Robb [this message]
2008-07-23 14:23 ` Wookey
2008-07-23 21:02 ` Bill Traynor
2008-07-24 8:45 ` Shaz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1216825175.12161.18.camel@samuelr.hq.netapp.com \
--to=sam@oneparticularharbor.net \
--cc=groupsecurityengineering@gmail.com \
--cc=linux-embedded@vger.kernel.org \
--cc=r.schwebel@pengutronix.de \
--cc=shazalive@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;
as well as URLs for NNTP newsgroup(s).