From: David Woodhouse <dwmw2@infradead.org>
To: Ingo Oeser <ioe-lkml@rameria.de>
Cc: linux-kernel@vger.kernel.org, git@vger.kernel.org
Subject: Re: Kernel headers git tree
Date: Fri, 14 Jul 2006 19:16:11 +0100 [thread overview]
Message-ID: <1152900971.3191.76.camel@pmac.infradead.org> (raw)
In-Reply-To: <200607142005.36998.ioe-lkml@rameria.de>
On Fri, 2006-07-14 at 20:05 +0200, Ingo Oeser wrote:
> 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?
Well, they're all derived from commits in Linus' tree. I could set up
another mailing list feed script which tracks it, but I'd like to give
it a while (until I'm happy with the export scripts) first.
--
dwmw2
next prev parent reply other threads:[~2006-07-14 18:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 23:59 Kernel headers git tree David Woodhouse
2006-07-14 0:39 ` Junio C Hamano
2006-07-14 0:56 ` David Woodhouse
2006-07-14 1:08 ` Linus Torvalds
2006-07-14 2:37 ` Junio C Hamano
2006-07-14 1:05 ` Linus Torvalds
2006-07-14 1:27 ` David Woodhouse
2006-07-14 5:16 ` Linus Torvalds
2006-07-14 10:23 ` David Woodhouse
2006-07-14 15:57 ` Linus Torvalds
2006-07-14 17:51 ` Daniel Barkalow
2006-07-14 17:58 ` David Woodhouse
2006-07-14 18:21 ` Daniel Barkalow
2006-07-14 5:52 ` Linus Torvalds
2006-07-14 9:38 ` David Woodhouse
2006-07-14 15:39 ` Linus Torvalds
2006-07-17 22:34 ` [PATCH] Trivial path optimization test Alex Riesen
2006-07-24 6:41 ` Junio C Hamano
2006-07-24 23:23 ` Alex Riesen
2006-07-24 23:23 ` Alex Riesen
2006-07-14 18:01 ` Kernel headers git tree Junio C Hamano
2006-07-14 18:21 ` David Woodhouse
2006-07-14 7:20 ` Ian Campbell
2006-07-14 7:52 ` Junio C Hamano
2006-07-14 18:05 ` Ingo Oeser
2006-07-14 18:16 ` David Woodhouse [this message]
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=1152900971.3191.76.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=git@vger.kernel.org \
--cc=ioe-lkml@rameria.de \
--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 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.