From: Ingo Oeser <ioe-lkml@rameria.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-kernel@vger.kernel.org, git@vger.kernel.org
Subject: Re: Kernel headers git tree
Date: Fri, 14 Jul 2006 20:05:35 +0200 [thread overview]
Message-ID: <200607142005.36998.ioe-lkml@rameria.de> (raw)
In-Reply-To: <1152835150.31372.23.camel@shinybook.infradead.org>
Hi David,
On Friday, 14. July 2006 01:59, David Woodhouse wrote:
> Only commits in Linus' tree which actually affect the exported result
> should have an equivalent commit in the above tree, which means that any
> changes which affect userspace should be clearly visible for review.
Where can I subscribe for commit messages there?
Every serious systems programmer (for Linux) will ask this question soon :-)
Maybe one of the Postmasters at vger.kernel.org can setup
a mailing list for this.
Regards
Ingo Oeser, happy to see this project finally there
next prev parent reply other threads:[~2006-07-14 18:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 23:59 Kernel headers git tree David Woodhouse
2006-07-14 7:20 ` Ian Campbell
2006-07-14 18:05 ` Ingo Oeser [this message]
2006-07-14 18:16 ` David Woodhouse
2006-07-18 21:15 ` Ingo Oeser
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=200607142005.36998.ioe-lkml@rameria.de \
--to=ioe-lkml@rameria.de \
--cc=dwmw2@infradead.org \
--cc=git@vger.kernel.org \
--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