From: Andrew Beverley <andy@andybev.com>
To: "John A. Sullivan III" <jsullivan@opensourcedevel.com>
Cc: lartc@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Cross posting
Date: Tue, 27 Dec 2011 19:00:44 +0000 [thread overview]
Message-ID: <1325012444.14018.141.camel@steve-pc> (raw)
In-Reply-To: <1324938391.4401.75.camel@denise.theartistscloset.com>
On Mon, 2011-12-26 at 17:26 -0500, John A. Sullivan III wrote:
> Hello, all. I still find myself posting most of my questions to
> netdev@vger.kernel.org since I'm not quite sure who has found there way
> to lartc yet.
>
> I know it is normally considered rude to cross post but would it be a
> good idea to cross post until lartc builds up a support community of its
> own and to help build its archives? Thoughts? Comments? Insults? Thanks
I personally think that in this case it would be a good thing to
cross-post.
Andy
next prev parent reply other threads:[~2011-12-27 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-26 22:26 Cross posting John A. Sullivan III
2011-12-27 10:30 ` Niccolò Belli
2011-12-27 19:00 ` Andrew Beverley [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-26 22:49 Jean-baptiste Théou
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=1325012444.14018.141.camel@steve-pc \
--to=andy@andybev.com \
--cc=jsullivan@opensourcedevel.com \
--cc=lartc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).