From: George Dunlap <George.Dunlap@citrix.com>
To: Wei Liu <wl@xen.org>
Cc: Nick Rosbrook <rosbrookn@ainfosec.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Ian Jackson <Ian.Jackson@citrix.com>
Subject: Re: [PATCH] golang: Update generated files after libxl_types.idl change
Date: Fri, 22 May 2020 10:32:51 +0000 [thread overview]
Message-ID: <3FE58AF4-3C20-4615-A28C-31273C4BF301@citrix.com> (raw)
In-Reply-To: <20200522100145.w6xd5v7ioubzkni5@liuwe-devbox-debian-v2.j3c5onc20sse1dnehy4noqpfcg.zx.internal.cloudapp.net>
> On May 22, 2020, at 11:01 AM, Wei Liu <wl@xen.org> wrote:
>
> On Fri, May 22, 2020 at 10:49:56AM +0100, George Dunlap wrote:
>> c/s 7efd9f3d45 ("libxl: Handle Linux stubdomain specific QEMU
>> options.") modified libl_types.idl. Run gengotypes.py again to update
>
> libxl_types.idl.
>
>> the geneated golang bindings.
>>
>
> Can we perhaps add a dependency on golang's side such that it can be
> auto-generated in the future?
Indeed, I’m trying to think of a good solution to this.
-George
prev parent reply other threads:[~2020-05-22 10:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 9:49 [PATCH] golang: Update generated files after libxl_types.idl change George Dunlap
2020-05-22 10:01 ` Wei Liu
2020-05-22 10:32 ` George Dunlap [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=3FE58AF4-3C20-4615-A28C-31273C4BF301@citrix.com \
--to=george.dunlap@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=rosbrookn@ainfosec.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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).