From: Yolkfull Chow <yzhou@redhat.com>
To: Lucas Meneghel Rodrigues <lmr@redhat.com>
Cc: kvm@vger.kernel.org, autotest@test.kernel.org
Subject: Re: [Autotest] [PATCH] Fix a bug in function create in kvm_vm
Date: Mon, 12 Oct 2009 14:58:05 +0800 [thread overview]
Message-ID: <20091012065805.GC2501@aFu.nay.redhat.com> (raw)
In-Reply-To: <1255305185.3849.2021.camel@localhost.localdomain>
On Sun, Oct 11, 2009 at 08:53:05PM -0300, Lucas Meneghel Rodrigues wrote:
> On Sat, 2009-10-10 at 16:48 +0800, Yolkfull Chow wrote:
> > On Sat, Oct 10, 2009 at 04:24:45PM +0800, Yolkfull Chow wrote:
> > > On Mon, Oct 05, 2009 at 04:03:22PM -0300, Lucas Meneghel Rodrigues wrote:
> > > > Hi Yolkfull! I've checked your patch, but it turns out that the comma
> > > > is valid syntax for the logging module. By any chance you actually had
> > > > an error with it?
> > >
> > > Hi Lucas,
> > > I just checked, yes it's valid syntax for this module. Before this I met
> > > a traceback during running autotest and it indicated this line
> > > around,thus I doubt about this by mistake. Sorry for confusing. ;-)
> > >
> > > But I found for the variables in logging.debug(),sometimes it use comma
> > > to format while sometimes '%' which will drop code readability.
> >
> > Another reason is if someone who still using kvm_log want to backport
> > codes from this tree, not only need he replace all 'logging' with
> > 'kvm_log' but also need change these comma syntax. ;-)
>
> Yes, we prefer using comma on logging statements allways, but sometimes
> we make mistakes and use the standard string format with %.
>
> When porting code, try to keep in mind that and try to use allways the
> comma, but don't worry too much about it... just general guidelines :)
Ok, that could be the style. Thanks very much for remind. :)
Cheers,
>
> Lucas
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-10-12 6:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 7:45 [PATCH] Fix a bug in function create in kvm_vm Yolkfull Chow
2009-10-05 19:03 ` [Autotest] " Lucas Meneghel Rodrigues
2009-10-10 8:24 ` Yolkfull Chow
2009-10-10 8:48 ` Yolkfull Chow
2009-10-11 23:53 ` Lucas Meneghel Rodrigues
2009-10-12 6:58 ` Yolkfull Chow [this message]
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=20091012065805.GC2501@aFu.nay.redhat.com \
--to=yzhou@redhat.com \
--cc=autotest@test.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=lmr@redhat.com \
/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.