From: Andrew Morton <akpm@osdl.org>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: jdike@addtoit.com, linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net,
bstroesser@fujitsu-siemens.com
Subject: Re: [patch 0/6] latest bugfixes for 2.6.12
Date: Mon, 9 May 2005 16:45:46 -0700 [thread overview]
Message-ID: <20050509164546.0d6d136b.akpm@osdl.org> (raw)
In-Reply-To: <200505100110.16920.blaisorblade@yahoo.it>
Blaisorblade <blaisorblade@yahoo.it> wrote:
>
> Here are some more fixes intended for 2.6.12 (and well tested). Can you merge
> them soon, Andrew? Thanks.
Sure.
> The first is a particularly bad one since it shows up when you *start*
> compiling UML (due to a quilt patch -> normal patch conversion problem, a
> file wasn't actually deleted, but it was when applied through quilt). Was
> this too quick a merge, maybe? What's your "merging policy" (if any) for
> patches?
Jeff sent in fixes which were dependent on other things I had, we're maybe
several weeks away from 2.6.12, so I figured there was plenty of time to
get things fixed up - best to get it all flushed out and fix any fallout
rather than hang around, given that UML seems to be still changing in
fairly significant ways.
next prev parent reply other threads:[~2005-05-09 23:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 23:10 Blaisorblade
2005-05-09 23:45 ` Andrew Morton [this message]
2005-05-09 23:39 ` Blaisorblade
2005-05-10 0:02 ` Andrew Morton
2005-05-10 10:17 ` Blaisorblade
2005-05-10 10:42 ` Andrew Morton
2005-05-10 10:43 ` Restoring the link to snapshots on kernel.org (was: Re: [uml-devel] Re: [patch 0/6] latest bugfixes for 2.6.12) Blaisorblade
2005-05-10 16:03 ` Restoring the link to snapshots on kernel.org H. Peter Anvin
2005-05-10 16:11 ` Lee Revell
2005-05-10 21:14 ` H. Peter Anvin
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=20050509164546.0d6d136b.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=blaisorblade@yahoo.it \
--cc=bstroesser@fujitsu-siemens.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome