From: Thomas Huth <thuth@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Max Reitz <mreitz@redhat.com>, Qemu-block <qemu-block@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: Pre-Christmas meeting notes
Date: Thu, 9 Jan 2020 17:29:31 +0100 [thread overview]
Message-ID: <4626afdf-ffe9-580c-fe75-f8f2aa506235@redhat.com> (raw)
In-Reply-To: <23ba22f5-2990-3821-cfb9-7d448c65240a@virtuozzo.com>
On 09/01/2020 16.03, Vladimir Sementsov-Ogievskiy wrote:
> 06.01.2020 20:15, Max Reitz wrote:
>> Misc
>> ----
>>
>> The Wiki’s TODO list is horribly outdated. What should we do about
>> it? Maybe archive it and start a new one? (Most of the things on the
>> current list are either done or we don’t want to do anymore.)
>
>
> May be, create block/TODO.txt instead? It would be simpler to manage file
> in git than wiki page.
Is it? We removed a bunch of stale TODO files in the past already:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=d494d79eabfdac0
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=9e564a1dde5abc7
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=ba43da36983a0bf
And there are some more TODO files in the target/ subfolders which look
also quite stale... so I somewhat doubt that a TODO list in git is much
better than a TODO list in the wiki.
Maybe we just need a proper bug/feature tracker instead (since Launchpad
is IMHO quite a bad choice for bug tracking, too)...
Thomas
prev parent reply other threads:[~2020-01-09 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 17:15 Pre-Christmas meeting notes Max Reitz
2020-01-09 15:03 ` Vladimir Sementsov-Ogievskiy
2020-01-09 16:29 ` Thomas Huth [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=4626afdf-ffe9-580c-fe75-f8f2aa506235@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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 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).