From: Rob Landley <rob@landley.net>
To: Jeff Dike <jdike@addtoit.com>
Cc: Blaisorblade <blaisorblade@yahoo.it>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: merge status
Date: Fri, 18 Nov 2005 17:37:12 -0600 [thread overview]
Message-ID: <200511181737.12428.rob@landley.net> (raw)
In-Reply-To: <20051118235231.GB12049@ccure.user-mode-linux.org>
On Friday 18 November 2005 17:52, Jeff Dike wrote:
> > > 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.
>
> And you're welcome to send directly to Andrew, but feel free to send
> them to me beforehand.
Can I second the "send UML patches to Jeff and let him send them on to
Andrew/Linus" approach? Please? It makes it much easier for me to test,
with a known working system plus UML-only changes...
> Jeff
Rob
-------------------------------------------------------
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 23:37 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 21:35 merge status Andrew Morton
2005-11-09 21:50 ` James Bottomley
2005-11-09 22:01 ` Linus Torvalds
2005-11-09 22:25 ` James Bottomley
2005-11-09 22:43 ` Linus Torvalds
2005-11-10 7:16 ` Jeff Garzik
2005-11-09 23:01 ` Andrew Morton
2005-11-09 23:09 ` Jesper Juhl
2005-11-09 23:58 ` Linus Torvalds
2005-11-10 13:28 ` Pavel Machek
2005-11-16 13:36 ` [uml-devel] " Rob Landley
2005-11-18 7:08 ` Blaisorblade
2005-11-18 7:17 ` Rob Landley
2005-11-18 7:51 ` Blaisorblade
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 [this message]
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
2005-11-10 0:16 ` Con Kolivas
2005-11-10 0:25 ` Andrew Morton
2005-11-10 0:24 ` James Bottomley
2005-11-10 8:40 ` Jens Axboe
2005-11-10 8:56 ` Andrew Morton
2005-11-10 9:22 ` Jens Axboe
2005-11-10 9:30 ` Andrew Morton
2005-11-10 9:57 ` git branches strategy (was Re: merge status) Jeff Garzik
2005-11-10 13:22 ` merge status Dave Kleikamp
2005-11-10 13:26 ` Pavel Machek
2005-11-14 20:13 ` Bill Davidsen
2005-11-09 22:05 ` Roland Dreier
2005-11-09 22:12 ` Jody McIntyre
2005-11-09 22:18 ` Linus Torvalds
2005-11-09 22:23 ` Jody McIntyre
2005-11-09 22:45 ` Andrew Morton
2005-11-09 22:48 ` Linus Torvalds
2005-11-09 22:13 ` Anton Altaparmakov
2005-11-09 22:48 ` Andrew Morton
2005-11-09 22:58 ` Linus Torvalds
2005-11-09 22:41 ` Russell King
2005-11-10 7:20 ` Jeff Garzik
2005-11-10 8:41 ` Jens Axboe
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=200511181737.12428.rob@landley.net \
--to=rob@landley.net \
--cc=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.