From: Jan Kiszka <jan.kiszka@web.de>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: linuxram@us.ibm.com, qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [COMMIT 707c0db] support colon in filenames
Date: Sat, 04 Jul 2009 13:13:43 +0200 [thread overview]
Message-ID: <4A4F3967.9040106@web.de> (raw)
In-Reply-To: <200906300055.n5U0tAD8013302@d03av01.boulder.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 413 bytes --]
Anthony,
please revert this patch until Ram Pai provides a better version. It
causes too many problems. At least it
- breaks -pflash somefile -snapshot
- breaks mingw32 build due to redefined _open
- uses PATH_MAX
rev3 does not fix any of the above.
At this chance: there is at least one indention issue remaining in
fill_token() which would be nice to fix while reworking the patch.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next parent reply other threads:[~2009-07-04 11:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200906300055.n5U0tAD8013302@d03av01.boulder.ibm.com>
2009-07-04 11:13 ` Jan Kiszka [this message]
2009-07-05 21:47 ` [Qemu-devel] Re: [COMMIT 707c0db] support colon in filenames Jan Kiszka
2009-07-06 16:28 ` Ram Pai
2009-07-07 18:29 ` Jan Kiszka
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=4A4F3967.9040106@web.de \
--to=jan.kiszka@web.de \
--cc=aliguori@us.ibm.com \
--cc=linuxram@us.ibm.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).