From: Jeff Dike <jdike@addtoit.com>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: [patch 0/17] UML updates, which must be merged before 2.6.9
Date: Mon, 18 Oct 2004 17:16:26 -0400 [thread overview]
Message-ID: <200410182116.i9ILGQUA013137@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Fri, 15 Oct 2004 00:44:47 +0200." <200410150044.47234.blaisorblade_spam@yahoo.it>
blaisorblade_spam@yahoo.it said:
> About other work - could you drop the outdated SKAS patches from the
> official page? Updating two sites is slow, and waiting for you to
> pull the changes from CVS makes the CVS actually unusable (plus you
> must do the fucking "SF.net download dance", which I experienced
> too!).
I'd still like to be available on the main site, unless you totally don't
want that. In that case, I'll drop the current patches (or make them less
visible) and add a pointer off to your site.
Jeff
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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:[~2004-10-18 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 1:05 [uml-devel] [patch 0/17] UML updates, which must be merged before 2.6.9 BlaisorBlade
[not found] ` <200410130040.i9D0eA3P004443@ccure.user-mode-linux.org>
2004-10-14 22:44 ` [uml-devel] " BlaisorBlade
2004-10-18 21:16 ` Jeff Dike [this message]
2004-10-18 22:20 ` BlaisorBlade
2004-10-22 1:32 ` Jeff Dike
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=200410182116.i9ILGQUA013137@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade_spam@yahoo.it \
--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