From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Rob Landley <rob@landley.net>
Subject: Re: [uml-devel] Re: merge status
Date: Fri, 18 Nov 2005 08:51:38 +0100 [thread overview]
Message-ID: <200511180851.38683.blaisorblade@yahoo.it> (raw)
In-Reply-To: <200511180117.03742.rob@landley.net>
On Friday 18 November 2005 08:17, Rob Landley wrote:
> On Friday 18 November 2005 01:08, Blaisorblade wrote:
> > On Wednesday 16 November 2005 14:36, Rob Landley wrote:
> > > Linus said this:
Btw, where does this quote come from?
> > > > I think one reason -mm has worked so damn well (apart from you being
> > > > "The Calmest Man on Earth"(tm)) is because it's essentially been that
> > > > buffer for anything non-trivial. Sometimes the "n+2" has been a lot
> > > > more than "n+2" in fact, and that's often good.
> > > >
> > > > (And at the same time, -mm has enough visibility that it doesn't
> > > > drive developers crazy even when the "n+2" ends up being "n+5" or
> > > > somethiing).
I don't quite get this +2/+5 discussion.
> > > > I'd _hope_ that the same kind of situation could work for some of the
> > > > majos subsystem git trees too: where the maintainer tree is well
> > > > enough known that it gets sufficient coverage for that area that a
> > > > "+2" approach for merging into the default kernel is practical.
> > > >
> > > > I also think it certainly _should_ be possible for the big areas that
> > > > have well-defined target audiences.
> > Definitely Jeff's tree is a first filter for his work, but I've not seen
> > it working a lot as a collector, especially for little fixes - but there
> > it makes sense.
> > I tend to send directly to Andrew and he forwards them to Linus (in many
> > cases so fast that I wonder if they appear in one -mm release), but I
> > currently do not have a public tree.
> So there currently _is_ no one UML tree that people interested in the most
> recent UML developments can check out. We basically have to wait until it
> hits mainline.
Patches go in -mm first. Currently Andrew is often very quick at merging them.
Also, fixups tend to have less needs for testing - and they're often
backported to -bs.
Also, I don't tend to merge big patches without first checking.
> That's sad. I think I'll stick with Jeff's tree as the closest I've come
> so far...
> > > And applied them all (in series order) with a for loop.
> >
> > Can I suggest using quilt for this (as it's more powerful and easy to
> > use)?
> >
> > Especially when you add other patches as compile fixups...
> I'm not applying the other patches at the moment. Right now I'm just
> trying to get Jeff's tree to build for me.
Which means applying your own fixups.
> If I have time tonight I'm
> going to cherry-pick his patch list to see which ones I can get to compile,
> and give him the list of each one that breaks my build (and how).
I suggest quilt exactly because it automates one big task - managing the
stacks of applied and unapplied patches. Will "patch" suggest you which patch
is the top one? Quilt will. That's why I suggest you to try it.
> I just
> mentioned that #2 of the recent 4 sent to Andrew broke the build for me,
> but that's not the only breakage I see from Jeff's tree. (I currently have
> access to four different build environments. I was focusing on the PLD
> x86-64 system I'm borrowing, but right now I'm focusing on my ubuntu
> laptop. Then knoppix, and then my Linux From Scratch system with gcc 4.0.2
> and uClibc...
> Expect to be hearing from me a lot. :)
No problem... just be patient for fixes. And IMHO you shouldn't feel so shy
about fixing such compile problems (no complaining!) I don't expect you to
debug the stub problems, but the rest should be easier to work with.
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Messenger: chiamate gratuite in tutto il mondo
http://it.messenger.yahoo.com
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&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
next prev parent reply other threads:[~2005-11-18 7:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051109133558.513facef.akpm@osdl.org>
[not found] ` <20051109150141.0bcbf9e3.akpm@osdl.org>
[not found] ` <Pine.LNX.4.64.0511091547160.4627@g5.osdl.org>
2005-11-16 13:36 ` [uml-devel] Re: merge status Rob Landley
2005-11-18 7:08 ` Blaisorblade
2005-11-18 7:17 ` Rob Landley
2005-11-18 7:51 ` Blaisorblade [this message]
2005-11-18 8:41 ` Rob Landley
2005-11-19 2:33 ` Blaisorblade
2005-11-19 3:26 ` Rob Landley
[not found] ` <87hda65mbv.fsf@amaterasu.srvr.nix>
2005-11-21 14:51 ` Rob Landley
2005-11-21 19:41 ` Nix
2005-11-19 23:40 ` Henrik Nordstrom
2005-11-20 16:32 ` Blaisorblade
2005-11-18 23:52 ` Jeff Dike
2005-11-18 23:37 ` Rob Landley
2005-11-19 0:55 ` Jeff Dike
2005-11-19 0:06 ` Rob Landley
2005-11-30 17:23 ` Michael Richardson
2005-12-02 0:15 ` Blaisorblade
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=200511180851.38683.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=rob@landley.net \
--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