On Wed, Dec 2, 2015 at 7:19 AM, Nils Chr. Brause
wrote:
> On Wed, Dec 2, 2015 at 11:48 AM, Auke Booij wrote:
> > I'd be happy to rebase against that, but since that hasn't been merged
> > yet, I thought I'd take the current tree as a a basis.
> >
> > If
On Sun, Nov 29, 2015 at 01:54:46PM +, Auke Booij wrote:
> The enum attribute, for which scanner support was introduced in
> 1771299, can be used to link message arguments to s. However,
> some arguments refer to s in a different .
>
> This adds scanner support for referring to an in a
Looks correct to me.
I had a slightly different patch in patchwork which changes
protocol-to-docbook. It puts the enumeration into it's own statement,
rather than a nested if statement, and it adds the object:: prefix to the
documentation for all enumerations, not just the cross-object ones.
On
On Wed, Dec 2, 2015 at 11:48 AM, Auke Booij wrote:
> I'd be happy to rebase against that, but since that hasn't been merged
> yet, I thought I'd take the current tree as a a basis.
>
> If you think having the interface:: prefix everywhere makes sense, I
> can change that if you
I'd be happy to rebase against that, but since that hasn't been merged
yet, I thought I'd take the current tree as a a basis.
If you think having the interface:: prefix everywhere makes sense, I
can change that if you want.
On 2 December 2015 at 03:09, Bill Spitzak wrote:
>
The enum attribute, for which scanner support was introduced in
1771299, can be used to link message arguments to s. However,
some arguments refer to s in a different .
This adds scanner support for referring to an in a different
using dot notation. It also sets the attributes in this
style in