linux-um archives
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: David Howells <dhowells@redhat.com>
Cc: jdike@karaya.com, torvalds@osdl.org,
	linux-kernel@vger.kernel.org,
	user-mode-linux-devel@lists.sourceforge.net,
	linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [uml-devel] GIT pull on work_struct reduction tree
Date: Tue, 5 Dec 2006 12:16:32 -0800	[thread overview]
Message-ID: <20061205121632.65572efb.akpm@osdl.org> (raw)
In-Reply-To: <24327.1165348363@redhat.com>

On Tue, 05 Dec 2006 19:52:43 +0000
David Howells <dhowells@redhat.com> wrote:

> I've brought the work_struct reduction patches up to date.  They're in a GIT
> tree for you to pull when you're ready.

Given that I (and probably many others) now have a pile of build errors to
fix, it would be nice to have a short-but-full description of what one must
do to fix those up, please.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2006-12-05 20:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20061122130222.24778.62947.stgit@warthog.cambridge.redhat.com>
2006-12-05 19:52 ` [uml-devel] GIT pull on work_struct reduction tree David Howells
2006-12-05 20:16   ` Andrew Morton [this message]
2006-12-05 21:05     ` Stefan Richter
2006-12-05 21:41     ` David Howells

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=20061205121632.65572efb.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=dhowells@redhat.com \
    --cc=jdike@karaya.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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