From: Andi Kleen <ak-l3A5Bk7waGM@public.gmane.org>
To: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
Cc: andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [Bug 1656] Merge FreeBSD local changes into vendor dist (fwd)
Date: Wed, 10 Dec 2003 12:05:22 +0100 [thread overview]
Message-ID: <20031210120522.0d75d649.ak@suse.de> (raw)
In-Reply-To: <20031209142631.F43549-Y6VGUYTwhu0@public.gmane.org>
On Tue, 9 Dec 2003 14:32:34 -0800 (PST)
Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org> wrote:
> I believe my solution will be to obfuscate any non-Linux identifying
> features from future bug submissions to keep them out of sight of the
> pedants^H^H^H^H^H^H^H admins who have nothing better to do than cancel
> legitimate bug reports.
Better would be probably just to tell the Bugme janitors about the special situation
about ACPI bugs and get their agreement to keep these bugs open. Obfuscating
non Linux specific bugs doesn't sound like a good idea.
-Andi
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
next prev parent reply other threads:[~2003-12-10 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-09 17:59 [Bug 1656] Merge FreeBSD local changes into vendor dist (fwd) Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A8470255EFB2-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-12-09 22:32 ` Nate Lawson
[not found] ` <20031209142631.F43549-Y6VGUYTwhu0@public.gmane.org>
2003-12-10 11:05 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-10 3:01 Yu, Luming
2003-12-09 17:22 Nate Lawson
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=20031210120522.0d75d649.ak@suse.de \
--to=ak-l3a5bk7wagm@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=nate-Y6VGUYTwhu0@public.gmane.org \
--cc=robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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