From: Pavel Machek <pavel@ucw.cz>
To: Jiri Kosina <jkosina@suse.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: linux-next as a plain diff ?
Date: Thu, 26 Mar 2009 21:14:44 +0100 [thread overview]
Message-ID: <20090326201444.GA29836@elf.ucw.cz> (raw)
In-Reply-To: <alpine.LRH.2.00.0903261531000.8561@twin.jikos.cz>
On Thu 2009-03-26 15:33:06, Jiri Kosina wrote:
> On Thu, 26 Mar 2009, Pavel Machek wrote:
>
> > Is there linux-next available somewhere as a plain diff? I'd like to
> > look at tomoyo changes... unfortunately that does not seem exactly easy.
> > I thought that maybe -mm could help, but... latest -mm listed on
> > kernel.org is for 2.6.28-rc2-mm1....
>
> You could either extract it trivially directly form -next git repository,
> or get a (always little bit outdated) version from
> http://userweb.kernel.org/~akpm/mmotm/broken-out/linux-next.patch
Thanks! The last url is what I was looking for.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-03-26 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 10:05 linux-next as a plain diff ? Pavel Machek
2009-03-26 14:33 ` Jiri Kosina
2009-03-26 20:14 ` Pavel Machek [this message]
2009-03-26 15:22 ` Randy Dunlap
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=20090326201444.GA29836@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=jkosina@suse.cz \
--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