From: Matt Zimmerman <mdz@debian.org>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] uml-patch-2.4.20-7
Date: Wed, 3 Sep 2003 11:45:06 -0400 [thread overview]
Message-ID: <20030903154506.GL7304@alcor.net> (raw)
In-Reply-To: <200309021900.h82J0YHx001746@ccure.karaya.com>
On Tue, Sep 02, 2003 at 03:00:34PM -0400, Jeff Dike wrote:
> Since I can't break the existing
> ubdx=cow-file,backing-file
> syntax, that will need to continue to be supported.
Maybe it wouldn't be so bad to break the existing
ubdx=cow-file
syntax, though?
--
- mdz
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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:[~2003-09-03 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200308071929.h77JTo5N017958@uml.karaya.com>
[not found] ` <3F512995.4050209@vgertech.com>
2003-09-02 19:00 ` [uml-devel] uml-patch-2.4.20-7 Jeff Dike
2003-09-03 15:45 ` Matt Zimmerman [this message]
2003-09-04 2:30 ` Jeff Dike
2003-09-04 3:15 ` Matt Zimmerman
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=20030903154506.GL7304@alcor.net \
--to=mdz@debian.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