From: Ingo Schwarze <schwarze@usta.de>
To: tech@mdocml.bsd.lv
Subject: Re: [PATCH] rudimentary .ds support
Date: Sat, 3 Jul 2010 17:55:52 +0200 [thread overview]
Message-ID: <20100703155552.GB4327@iris.usta.de> (raw)
In-Reply-To: <4C2F2652.2090403@bsd.lv>
Hi Kristaps,
> I see the utility of this, but would like the functions accessed
> through regs.h,
Yes, that makes sense, thanks for the suggestion.
> either within struct regset itself or as its own
> structure with setters and getters.
I prefer the latter.
The singly linked list won't be the last word on this,
so the interface should allow reimplementation in terms
of more efficient data structures.
[...]
> Other than that, it looks fine. Needs bits in html.c (I can do
> this, if you don't want to muck around in there)
Yes, that would be kind, thanks.
> and roff.3 (including the current short-comings).
Done.
Of course, i have only documented those parts relevant for
section 3, not the frontend issues.
Thanks for checking,
Ingo
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2010-07-03 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-03 6:39 Ingo Schwarze
2010-07-03 12:00 ` Kristaps Dzonsons
2010-07-03 15:55 ` Ingo Schwarze [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=20100703155552.GB4327@iris.usta.de \
--to=schwarze@usta.de \
--cc=tech@mdocml.bsd.lv \
/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).