From: George Dunlap <George.Dunlap@citrix.com>
To: Nick Rosbrook <rosbrookn@gmail.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>, Wei Liu <wl@xen.org>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
Nick Rosbrook <rosbrookn@ainfosec.com>,
Jan Beulich <jbeulich@suse.com>,
Ian Jackson <Ian.Jackson@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 1/3] golang/xenlight: re-track generated go code
Date: Tue, 12 May 2020 14:48:12 +0000 [thread overview]
Message-ID: <772DD16D-DA6B-4009-8B9B-B8187ED06136@citrix.com> (raw)
In-Reply-To: <2ccb1ae4ffa3f00a13ce303df0e4a44d249861c2.1588282027.git.rosbrookn@ainfosec.com>
> On Apr 30, 2020, at 10:38 PM, Nick Rosbrook <rosbrookn@gmail.com> wrote:
>
> Commit df669de074c395a3b2eeb975fddd3da4c148da13 un-tracked the generated
> Go code, but it was decided that we actually keep the generated code
> in-tree.
>
> Undo the changes to ignore the generated code, and re-generate it.
>
> Signed-off-by: Nick Rosbrook <rosbrookn@ainfosec.com>
Reviewed-by: George Dunlap <george.dunlap@citrix.com>
next prev parent reply other threads:[~2020-05-12 14:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 21:38 [PATCH 0/3] initialize xenlight go module Nick Rosbrook
2020-04-30 21:38 ` [PATCH 1/3] golang/xenlight: re-track generated go code Nick Rosbrook
2020-05-12 14:48 ` George Dunlap [this message]
2020-04-30 21:39 ` [PATCH 2/3] golang/xenlight: init xenlight go module Nick Rosbrook
2020-05-12 14:36 ` George Dunlap
2020-05-12 15:06 ` Nick Rosbrook
2020-05-12 15:47 ` George Dunlap
2020-05-12 15:58 ` Nick Rosbrook
2020-05-12 17:30 ` George Dunlap
2020-05-12 17:37 ` George Dunlap
2020-05-12 23:36 ` Nick Rosbrook
2020-04-30 21:39 ` [PATCH 3/3] golang/xenlight: add necessary module/package documentation Nick Rosbrook
2020-05-12 17:20 ` George Dunlap
2020-05-12 21:59 ` Nick Rosbrook
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=772DD16D-DA6B-4009-8B9B-B8187ED06136@citrix.com \
--to=george.dunlap@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=rosbrookn@ainfosec.com \
--cc=rosbrookn@gmail.com \
--cc=sstabellini@kernel.org \
--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 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.