From: DervishD <lartc@dervishd.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Where do I post patches?
Date: Thu, 09 Feb 2006 08:42:41 +0000 [thread overview]
Message-ID: <20060209084241.GA93@DervishD> (raw)
In-Reply-To: <1139455424.4283.35.camel@ras>
Hi Russell :)
* Russell Stuart <russell-lartc@stuart.id.au> dixit:
> I have found a few bugs in tc, and have produced patches
> for them. Two require changes to tc, one to the kernel.
>
> Where should I post these patches?
IMHO, you should start by posting the patches here for
peer-review and betatesting. After that, the kernel related patches
should be posted to LKML too.
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736 | http://www.dervishd.net
http://www.pleyades.net & http://www.gotesdelluna.net
It's my PC and I'll cry if I want to... RAmen!
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-02-09 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 3:23 [LARTC] Where do I post patches? Russell Stuart
2006-02-09 8:42 ` DervishD [this message]
2006-02-09 15:44 ` gypsy
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=20060209084241.GA93@DervishD \
--to=lartc@dervishd.net \
--cc=lartc@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