All of lore.kernel.org
 help / color / mirror / Atom feed
From: D Lambrou <dlambrou@crazylinux.net>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] 2.4.26 uml-patch
Date: 21 Apr 2004 01:37:38 +0300	[thread overview]
Message-ID: <1082500658.28003.1.camel@crazy> (raw)

Is there a 2.4.26 uml-patch ?? I tried applying 2.4.24-2 but with no
luck.

Thanks


-- 
---------------------------------------------------------
D Lambrou
http://crazylinux.net

You can always get my public key block from
http://crazylinux.net/public.asc
Fingerprint: C7B3 A112 3704 7202 2B33  6B28 5418 78DD 774A 7BCB



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&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:[~2004-04-20 22:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1082500658.28003.1.camel@crazy \
    --to=dlambrou@crazylinux.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 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.