On 01/21/2015 10:12 AM, Bastian Koppelmann wrote:
> Richard, before I put too much work into this. Are you happy with the general
> direction of this documentation?
Yes.
r~
On 01/14/2015 03:51 PM, Bastian Koppelmann wrote:
There is no overview, that shows all the frontend operation one can use, as
found on the wiki. Unfortunatly the wiki is out of date, so let's try to move
this documentation to the source files, which has the benefit, that it is easy
to update the
Richard Henderson writes:
> On 01/14/2015 10:15 AM, Lluís Vilanova wrote:
>> Sorry I wasn't clear. I meant that it might be better to remove tcg/README
>> and
>> instead document all the operations (those in the readme and the additional
>> ones) in the header.
> If we did that, it would go some
On 01/14/2015 10:15 AM, Lluís Vilanova wrote:
> Sorry I wasn't clear. I meant that it might be better to remove tcg/README and
> instead document all the operations (those in the readme and the additional
> ones) in the header.
If we did that, it would go somewhere else.
There are two different (
On 14 January 2015 at 18:15, Lluís Vilanova wrote:
> Sorry I wasn't clear. I meant that it might be better to remove tcg/README and
> instead document all the operations (those in the readme and the additional
> ones) in the header.
I think the IR is worth documenting in itself, rather than mergi
Bastian Koppelmann writes:
> On 01/14/2015 03:36 PM, Lluís Vilanova wrote:
>> Bastian Koppelmann writes:
>>
>>> There is no overview, that shows all the frontend operation one can use, as
>>> found on the wiki. Unfortunatly the wiki is out of date, so let's try to
>>> move
>>> this documentation
On 01/14/2015 03:51 PM, Bastian Koppelmann wrote:
There is no overview, that shows all the frontend operation one can use, as
found on the wiki. Unfortunatly the wiki is out of date, so let's try to move
this documentation to the source files, which has the benefit, that it is easy
to update the
On 01/14/2015 04:55 PM, Thomas Huth wrote:
On Wed, 14 Jan 2015 16:36:26 +0100
Lluís Vilanova wrote:
...
Also, AFAIR it was decided to use gtk-doc instead of doxygen.
If there's a consensus about which source code documentation style
should be used for QEMU, could you (or somebody else) maybe
On 01/14/2015 03:36 PM, Lluís Vilanova wrote:
Bastian Koppelmann writes:
There is no overview, that shows all the frontend operation one can use, as
found on the wiki. Unfortunatly the wiki is out of date, so let's try to move
this documentation to the source files, which has the benefit, that
On Wed, 14 Jan 2015 16:36:26 +0100
Lluís Vilanova wrote:
...
>
> Also, AFAIR it was decided to use gtk-doc instead of doxygen.
If there's a consensus about which source code documentation style
should be used for QEMU, could you (or somebody else) maybe add an
appropriate paragraph to the CODING
Bastian Koppelmann writes:
> There is no overview, that shows all the frontend operation one can use, as
> found on the wiki. Unfortunatly the wiki is out of date, so let's try to move
> this documentation to the source files, which has the benefit, that it is easy
> to update the documentation, i
There is no overview, that shows all the frontend operation one can use, as
found on the wiki. Unfortunatly the wiki is out of date, so let's try to move
this documentation to the source files, which has the benefit, that it is easy
to update the documentation, if the frontend is changed. This patc
12 matches
Mail list logo
