linux-um.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: Andrew Morton <akpm@osdl.org>
Cc: jdike@addtoit.com, linux-kernel@vger.kernel.org,
	user-mode-linux-devel@lists.sourceforge.net,
	bstroesser@fujitsu-siemens.com
Subject: [uml-devel] Re: [patch 0/6] latest bugfixes for 2.6.12
Date: Tue, 10 May 2005 01:39:00 +0200	[thread overview]
Message-ID: <200505100139.02512.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20050509164546.0d6d136b.akpm@osdl.org>

On Tuesday 10 May 2005 01:45, Andrew Morton wrote:
> 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,
Several weeks away? Ok, that's nice to know, so we are not in a hurry 
(especially since I'm totally busy). When I'll have time I'll flush out the 
rest of what I have in my tree.
> 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.
Ok, I had guessed we were near to the release instead.
-- 
Paolo Giarrusso, aka Blaisorblade
Skype user "PaoloGiarrusso"
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade




-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
_______________________________________________
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:[~2005-05-09 23:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-09 23:10 [uml-devel] [patch 0/6] latest bugfixes for 2.6.12 Blaisorblade
2005-05-09 23:45 ` [uml-devel] " Andrew Morton
2005-05-09 23:39   ` Blaisorblade [this message]
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             ` [uml-devel] Re: 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=200505100139.02512.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=akpm@osdl.org \
    --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;
as well as URLs for NNTP newsgroup(s).