All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Niteesh G. S." <niteesh.gs@gmail.com>, John Snow <jsnow@redhat.com>
Cc: kwolf@redhat.com, vsementsov@virtuozzo.com, ehabkost@redhat.com,
	qemu-devel@nongnu.org, wainersm@redhat.com, armbru@redhat.com,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: RFC: Implementation of QMP documentation retrieval command
Date: Mon, 21 Jun 2021 16:58:17 +0200	[thread overview]
Message-ID: <6fb6d9d7-3af2-c487-a1d4-aa1140c5a54d@redhat.com> (raw)
In-Reply-To: <CAN6ztm8D4VMf7p-trHNHoOA+1kAXXufTTaHpbyNXZ5qO2_uuPg@mail.gmail.com>

Hi Niteesh,

On 6/16/21 5:48 PM, Niteesh G. S. wrote:
> Hello,
> 
> We now have a reasonably working prototype that is capable of
> sending/receiving
> commands/responses, syntax highlighting, and a simple notification
> system. The
> prototype can be found here
> https://gitlab.com/niteesh.gs/qemu/-/tree/aqmp-tui-prototype
> <https://gitlab.com/niteesh.gs/qemu/-/tree/aqmp-tui-prototype>
> Working on this prototype gives us a lot of hints on things to worry
> about and other
> ideas that were worth implementing. Our next goal is to start working on
> the real TUI
> based on this prototype.
> 
> One requested feature of the TUI was to show documentation for the
> commands typed.
> To achieve this, a QMP command that lets us query the documentation from
> QEMU has
> to be implemented and some discussion has already been done on it in a
> previous thread.
> I request all continue that discussion here and suggest ideas regarding
> implementation.
> The goal is to come up with something small and simple which can also be
> improved upon
> after the summer.
> 
> I have a simple implementation of the command that returns dummy
> documentation here
> https://gitlab.com/niteesh.gs/qemu/-/commit/796a41fb2840b9f3484c6fd5672e6fceb73acaef
> <https://gitlab.com/niteesh.gs/qemu/-/commit/796a41fb2840b9f3484c6fd5672e6fceb73acaef>

I noticed your mail got no comment, and realized you asked us to
review your patches apart from the mailing list. I am not sure
if this is an experiment or a misunderstanding, but so far it is
unlikely you get review external to the mailing list, because it
is not very practical to reviewers.

Maybe some reviewers are willing to look at your tree, but if you
are looking for a wider audience, I recommend you to follow this
process (which you already used!):
https://wiki.qemu.org/Contribute/SubmitAPatch#Submitting_your_Patches

Regards,

Phil.



  reply	other threads:[~2021-06-21 14:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16 15:48 RFC: Implementation of QMP documentation retrieval command Niteesh G. S.
2021-06-21 14:58 ` Philippe Mathieu-Daudé [this message]
2021-06-21 18:26   ` Niteesh G. S.
2021-06-22  9:35     ` Stefan Hajnoczi
2021-06-22 10:26       ` Daniel P. Berrangé
2021-06-22 11:04         ` Vladimir Sementsov-Ogievskiy
2021-06-22 18:57       ` Niteesh G. S.
2021-06-23  8:44         ` Stefan Hajnoczi

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=6fb6d9d7-3af2-c487-a1d4-aa1140c5a54d@redhat.com \
    --to=philmd@redhat.com \
    --cc=armbru@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=niteesh.gs@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vsementsov@virtuozzo.com \
    --cc=wainersm@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.