On Fri, Feb 09, 2018 at 08:59:12PM +0100, Halil Pasic wrote: > Regarding patch #1 please see also: > https://lists.oasis-open.org/archives/virtio/201802/msg00018.html
Fine by me. Can you please open an issue to track it? This makes it easier for me to start voting. If you would rather use github issues, that'd be great. There seem to be easy tools to work with their API, e.g. http://search.cpan.org/~fayland/Net-GitHub-0.93/lib/Net/GitHub/V3/Issues.pm We need to come up with a schema to keep the following info in github: - what is the issue title/short description - which version fixes the issue? - what is the proposed spec change? and then send a script that can get an issue # and print that, similar to virtio-jira.pl in virtio-admin. Help with that is very welcome but if you'd rather not you can just use jira for now. Pls remember to set fixed in to 1.1 and environment to reporter name and email (yourself). > Halil Pasic (2): > ccw: be more precise the semantic of revision 1 > introduction: simplify the designation of legacy > > content.tex | 2 +- > introduction.tex | 4 ++-- > 2 files changed, 3 insertions(+), 3 deletions(-) --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org For additional commands, e-mail: virtio-dev-h...@lists.oasis-open.org
