* [Qemu-devel] [PATCH] docs/writing-qmp-commands: fix a typo @ 2015-05-29 10:16 Chen Hanxiao 2015-06-02 14:38 ` Stefan Hajnoczi 0 siblings, 1 reply; 6+ messages in thread From: Chen Hanxiao @ 2015-05-29 10:16 UTC (permalink / raw) To: qemu-devel; +Cc: qemu-trivial s/interation/iteration Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com> --- docs/writing-qmp-commands.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/writing-qmp-commands.txt b/docs/writing-qmp-commands.txt index f3df206..ab1fdd3 100644 --- a/docs/writing-qmp-commands.txt +++ b/docs/writing-qmp-commands.txt @@ -598,7 +598,7 @@ stored in its "value" member. In our example, the "value" member is a pointer to an TimerAlarmMethod instance. Notice that the "current" variable is used as "true" only in the first -interation of the loop. That's because the alarm timer method in use is the +iteration of the loop. That's because the alarm timer method in use is the first element of the alarm_timers array. Also notice that QAPI lists are handled by hand and we return the head of the list. -- 2.1.0 ^ permalink raw reply related [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] [PATCH] docs/writing-qmp-commands: fix a typo 2015-05-29 10:16 [Qemu-devel] [PATCH] docs/writing-qmp-commands: fix a typo Chen Hanxiao @ 2015-06-02 14:38 ` Stefan Hajnoczi 0 siblings, 0 replies; 6+ messages in thread From: Stefan Hajnoczi @ 2015-06-02 14:38 UTC (permalink / raw) To: Chen Hanxiao; +Cc: qemu-trivial, qemu-devel [-- Attachment #1: Type: text/plain, Size: 305 bytes --] On Fri, May 29, 2015 at 06:16:07AM -0400, Chen Hanxiao wrote: > s/interation/iteration > > Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com> > --- > docs/writing-qmp-commands.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com> [-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
[parent not found: <1432632341-5201-1-git-send-email-chenhanxiao@cn.fujitsu.com>]
* Re: [Qemu-devel] [PATCH] docs/writing-qmp-commands: fix a typo [not found] <1432632341-5201-1-git-send-email-chenhanxiao@cn.fujitsu.com> @ 2015-05-28 11:32 ` Michael Tokarev [not found] ` <87twuwaoju.fsf@blackfin.pond.sub.org> 0 siblings, 1 reply; 6+ messages in thread From: Michael Tokarev @ 2015-05-28 11:32 UTC (permalink / raw) To: Chen Hanxiao, Markus Armbruster; +Cc: qemu-trivial, qemu-devel 26.05.2015 12:25, Chen Hanxiao wrote: > s/interation/iteration > > Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com> > --- > docs/writing-qmp-commands.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/docs/writing-qmp-commands.txt b/docs/writing-qmp-commands.txt > index f3df206..ab1fdd3 100644 > --- a/docs/writing-qmp-commands.txt > +++ b/docs/writing-qmp-commands.txt > @@ -598,7 +598,7 @@ stored in its "value" member. In our example, the "value" member is a pointer > to an TimerAlarmMethod instance. > > Notice that the "current" variable is used as "true" only in the first > -interation of the loop. That's because the alarm timer method in use is the > +iteration of the loop. That's because the alarm timer method in use is the > first element of the alarm_timers array. Also notice that QAPI lists are handled > by hand and we return the head of the list. Applied to -trivial, thank you! Marcus: I don't think such obvious and trivial changes needs to be re-sent to -devel. Ofcourse it is better to send things to -devel rigth away, but requiring to resent is a bit over the top. I think anyway :) /mjt ^ permalink raw reply [flat|nested] 6+ messages in thread
[parent not found: <87twuwaoju.fsf@blackfin.pond.sub.org>]
* Re: [Qemu-devel] [PATCH] docs/writing-qmp-commands: fix a typo [not found] ` <87twuwaoju.fsf@blackfin.pond.sub.org> @ 2015-05-28 12:27 ` Michael Tokarev 2015-05-28 14:05 ` Markus Armbruster 0 siblings, 1 reply; 6+ messages in thread From: Michael Tokarev @ 2015-05-28 12:27 UTC (permalink / raw) To: Markus Armbruster; +Cc: qemu-trivial, qemu-devel 28.05.2015 15:12, Markus Armbruster wrote: > Michael Tokarev <mjt@tls.msk.ru> writes: [] >> Marcus: I don't think such obvious and trivial changes needs to be re-sent >> to -devel. Ofcourse it is better to send things to -devel rigth away, but >> requiring to resent is a bit over the top. I think anyway :) > > Patches must be posted to -devel for review. > > If you accept patches sent just to -trivial, then the only post to > -devel will be your pull request, where it most probably won't get > review. Obvious typo fix in comment or doc don't really need a big review. That's where the "too trivial" border can be drawn. Just to be clear: I'm not, in any way, against posting things to -devel, things SHOULD be posted to -devel. But once a thing has been posted like this one, just to -trivial, and it really _is_ trivial and obvious, it is enough to say somehting among "This one is okay, but the next time please send to -devel too". Thanks, /mjt > Judging from my own experience, no patch is too trivial to screw up. > Play it safe, post to -devel for review always. Resending a trivial > patch isn't exactly a big burden :) > ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] [PATCH] docs/writing-qmp-commands: fix a typo 2015-05-28 12:27 ` Michael Tokarev @ 2015-05-28 14:05 ` Markus Armbruster 2015-05-28 14:08 ` Peter Maydell 0 siblings, 1 reply; 6+ messages in thread From: Markus Armbruster @ 2015-05-28 14:05 UTC (permalink / raw) To: Michael Tokarev; +Cc: qemu-trivial, qemu-devel Michael Tokarev <mjt@tls.msk.ru> writes: > 28.05.2015 15:12, Markus Armbruster wrote: >> Michael Tokarev <mjt@tls.msk.ru> writes: > [] >>> Marcus: I don't think such obvious and trivial changes needs to be re-sent >>> to -devel. Ofcourse it is better to send things to -devel rigth away, but >>> requiring to resent is a bit over the top. I think anyway :) >> >> Patches must be posted to -devel for review. >> >> If you accept patches sent just to -trivial, then the only post to >> -devel will be your pull request, where it most probably won't get >> review. > > Obvious typo fix in comment or doc don't really need a big review. > That's where the "too trivial" border can be drawn. I don't want us to get into the "is this trivial enough to go in without review" business. [...] ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] [PATCH] docs/writing-qmp-commands: fix a typo 2015-05-28 14:05 ` Markus Armbruster @ 2015-05-28 14:08 ` Peter Maydell 0 siblings, 0 replies; 6+ messages in thread From: Peter Maydell @ 2015-05-28 14:08 UTC (permalink / raw) To: Markus Armbruster; +Cc: qemu-trivial, Michael Tokarev, qemu-devel On 28 May 2015 at 15:05, Markus Armbruster <armbru@redhat.com> wrote: > Michael Tokarev <mjt@tls.msk.ru> writes: > >> 28.05.2015 15:12, Markus Armbruster wrote: >>> Patches must be posted to -devel for review. >>> >>> If you accept patches sent just to -trivial, then the only post to >>> -devel will be your pull request, where it most probably won't get >>> review. >> >> Obvious typo fix in comment or doc don't really need a big review. >> That's where the "too trivial" border can be drawn. > > I don't want us to get into the "is this trivial enough to go in without > review" business. Yes, in general I agree. Nothing in our documentation says "send only to -trivial", and it's not a very big deal to ask for a resend on the odd occasion somebody does it by mistake. thanks -- PMM ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2015-06-02 14:38 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2015-05-29 10:16 [Qemu-devel] [PATCH] docs/writing-qmp-commands: fix a typo Chen Hanxiao 2015-06-02 14:38 ` Stefan Hajnoczi [not found] <1432632341-5201-1-git-send-email-chenhanxiao@cn.fujitsu.com> 2015-05-28 11:32 ` Michael Tokarev [not found] ` <87twuwaoju.fsf@blackfin.pond.sub.org> 2015-05-28 12:27 ` Michael Tokarev 2015-05-28 14:05 ` Markus Armbruster 2015-05-28 14:08 ` Peter Maydell
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).