From: Piotr Hosowicz <piotr@hosowicz.com>
To: linux-kernel@vger.kernel.org
Subject: Where to submit bug report about linux-next?
Date: Wed, 28 Apr 2010 13:26:30 +0200 [thread overview]
Message-ID: <4BD81B66.5010809@example.com> (raw)
Hello,
Where should I submit a bug report about yesterday's and today's linux-next?
Regards,
Piotr Hosowicz
--
- Czy jest cukier w kostkach ?
- Nie ma.
- A jakas inna tania bombonierka? Dla tesciowej.
NP: Mark Knopfler - Monteleone
NB: 2.6.34-rc5-git8
next reply other threads:[~2010-04-28 11:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 11:26 Piotr Hosowicz [this message]
2010-04-28 11:56 ` Where to submit bug report about linux-next? Mark Brown
2010-04-28 13:01 ` Piotr Hosowicz
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=4BD81B66.5010809@example.com \
--to=piotr@hosowicz.com \
--cc=linux-kernel@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