On 02/12/2018 02:03 PM, Cornelia Huck wrote:
> On Fri, 9 Feb 2018 22:43:23 +0200
> "Michael S. Tsirkin" <m...@redhat.com> wrote:
> 
>> 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.
> 
> I'd vote (heh) to just use jira for now. Especially as I'd like to get
> the big batch of the packed ring updates out of the way before we start
> to tweak our tooling...
> 
>>
>> Help with that is very welcome but if you'd rather not you
>> can just use jira for now.


I had a look at the script mentioned above and the GitHub API. I'm not
too eager to do this GitHub issues support at the moment, so I'm going
to stick with Jira.

Regards,
Halil

>> 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

Reply via email to