public inbox for gentoo-kernel@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stefan Schweizer <genstef@gentoo.org>
To: gentoo-kernel@lists.gentoo.org
Subject: [gentoo-kernel]  Re: Creating kernel-misc herd and alias
Date: Thu, 10 May 2007 08:17:41 +0200	[thread overview]
Message-ID: <f1ude5$6g4$1@sea.gmane.org> (raw)
In-Reply-To: 464277FA.5040007@gentoo.org

Daniel Drake wrote:

> Hi,
> 
> It's about time we separated core kernel bugs from userspace/portage
> stuff.
> 
> If there are no objections I'm going to create a kernel-misc herd.
> linux-info/linux-mod/kernel-2 eclass bugs will go there. Also,
> metadata.xml for the following packages will be updated (which will in
> turn result in bugs for some of the below going to kernel-misc):
> 
> app-admin/addpatches
> app-doc/linux-device-drivers
> app-misc/fdutils
> app-misc/klive
> app-misc/zisofs-tools
> dev-libs/klibc
> net-misc/arpstar
> sys-apps/kexec-tools
> sys-devel/sparse
> sys-fs/avfs
> sys-fs/cloop
> sys-fs/ecryptfs-utils
> sys-fs/fuse
> sys-fs/gnomevfs-mount
> sys-fs/jfsutils
> sys-fs/lufis
> sys-fs/siefs
> sys-fs/sshfs-fuse
> sys-fs/unionfs
> sys-kernel/genkernel

There is already a genkernel herd

> sys-kernel/ksymoops
> sys-kernel/linux-docs
> sys-process/schedtool
> 
> Everyone on the kernel@gentoo.org mail alias will be copied over, but
> are of course free to remove themselves.

Thank you for doing this. I can reduce the level of mails then by adding
myself to kernel-misc@ only. I am not interested in kernel sources stuff
because I prefer manually downloading and patching

Best regards,
Stefan

-- 
gentoo-kernel@gentoo.org mailing list



  reply	other threads:[~2007-05-10  6:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10  1:40 [gentoo-kernel] Creating kernel-misc herd and alias Daniel Drake
2007-05-10  6:17 ` Stefan Schweizer [this message]
2007-05-10  8:44 ` Robin H. Johnson

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='f1ude5$6g4$1@sea.gmane.org' \
    --to=genstef@gentoo.org \
    --cc=gentoo-kernel@lists.gentoo.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