All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ram Pai <linuxram@us.ibm.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [COMMIT 707c0db] support colon in filenames
Date: Mon, 06 Jul 2009 09:28:08 -0700	[thread overview]
Message-ID: <1246897688.6429.89.camel@localhost> (raw)
In-Reply-To: <4A511F7B.6040504@web.de>

On Sun, 2009-07-05 at 23:47 +0200, Jan Kiszka wrote:
> Jan Kiszka wrote:
> > Anthony,
> > 
> > please revert this patch until Ram Pai provides a better version. It
> > causes too many problems. At least it
Jan,

Yes I am working on the next revision of the patch. 

> > 
> >  - breaks -pflash somefile -snapshot
> 
> Some more details on this: it's not just pflash that suffers, -snapshot
> was broken for raw images in general. Declaring file access as a
> protocol apparently has some unwanted side effects that first have to be
> resolved (check also bdrv_open2 /wrt realpath).

I do not entirely understand the side effect. I will see if I can figure
this out. It will certainly help if you can elaborate more?

> 
> >  - breaks mingw32 build due to redefined _open
> 
> Sorry, this obviously does not apply to the merged revision 2 but to
> rev3 which I had applied locally.
> 
> >  - uses PATH_MAX

PATH_MAX is not defined in mingw32 environment? 

> > 
> > 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.
> > 

yes. noted.

Thanks,
RP

> > Jan
> > 
> 
> Jan
> 
 

  reply	other threads:[~2009-07-06 16:28 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 ` [Qemu-devel] Re: [COMMIT 707c0db] support colon in filenames Jan Kiszka
2009-07-05 21:47   ` Jan Kiszka
2009-07-06 16:28     ` Ram Pai [this message]
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=1246897688.6429.89.camel@localhost \
    --to=linuxram@us.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=jan.kiszka@web.de \
    --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 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.