From: Sam Ravnborg <sam@ravnborg.org>
To: Kbuild <linux-kbuild@vger.kernel.org>,
Roman Zippel <zippel@linux-m68k.org>,
Randy Dunlap <rdunlap@xenotime.net>,
LKML <linux-kernel@vger.kernel.org>,
kbuild devel <kbuild-devel@lists.sourceforge.net>
Subject: kbuild mailing list has moved
Date: Thu, 18 Oct 2007 12:00:19 +0200 [thread overview]
Message-ID: <20071018100019.GA18671@uranus.ravnborg.org> (raw)
The vger postmasters has created linux-kbuild on my request.
The old list at sourceforge had a few issues:
- it was subscriber-only
- it were relying on moderation
And I could see several mails did not get to the list lately
so I decided this was a good time for a new list.
I already requested marc.info to archieve the new list -
and I dunno where else the old list was archieved but we
ought to update.
I have no access to the list of subscribers on the old list
so people will have to subscribe manually.
How to subscribe:
send a mail to: majordomo@vger.kernel.org
containing following text:
subscribe linux-kbuild
See also http://vger.kernel.org/vger-lists.html
Below is a patch to update MAINTAINERS in the kernel.
Note that I expect the list to cover both pure kbuild
but also kconfig stuff.
Sam
diff --git a/MAINTAINERS b/MAINTAINERS
index 10deabe..f978c60 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2178,7 +2178,7 @@ S: Maintained
KCONFIG
P: Roman Zippel
M: zippel@linux-m68k.org
-L: kbuild-devel@lists.sourceforge.net
+L: linux-kbuild@vger.kernel.org
S: Maintained
KDUMP
@@ -2207,6 +2207,7 @@ KERNEL BUILD (kbuild: Makefile, scripts/Makefile.*)
P: Sam Ravnborg
M: sam@ravnborg.org
T: git kernel.org:/pub/scm/linux/kernel/git/sam/kbuild.git
+L: linux-kbuild@vger.kernel.org
S: Maintained
KERNEL JANITORS
next reply other threads:[~2007-10-18 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 10:00 Sam Ravnborg [this message]
2007-10-18 10:19 ` [kbuild-devel] kbuild mailing list has moved Giacomo A. Catenazzi
2007-10-18 11:05 ` Sam Ravnborg
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=20071018100019.GA18671@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=zippel@linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.