>From the list below:

  27 cgi.c:
   4 dbm.c:
   5 dbm_map.c:
   // 3 eqn.c:
   5 html.c:
  20 main.c:
   2 man.c:
   2 man_html.c:
   5 man_macro.c:
   // 2 man_term.c:
   9 man_validate.c:
  37 mandocdb.c:
   2 manpath.c:
  23 mansearch.c:
   4 mdoc_html.c:
   // 10 mdoc_macro.c:
   1 mdoc_man.c:
   2 mdoc_term.c:
  43 mdoc_validate.c:
   6 read.c:
  13 roff.c:
   // 1 tag.c:
   // 1 tbl_layout.c:
   // 1 tbl_opts.c:
   6 term_ps.c:
  11 tree.c:

I've checked the commented (//) files so far and they look fine. You can
recheck or take new ones.
Unfortunately, I don't have as much time as I'd like to so this goes rather
slowly.



2016-08-09 18:41 GMT+02:00 attila <[email protected]>:

> Hi {Ingo,Darius,misc@},
>
> Ingo Schwarze <[email protected]> writes:
>
> > Hi Dariusz,
> >
> > Dariusz Sendkowski wrote on Sun, Aug 07, 2016 at 08:27:07PM +0200:
> >
> >> OK, but from which branch?
> >
> > We don't use branches in OpenBSD.
> > Just use the HEAD of the OpenBSD CVS repository.
> >
> > You don't need to worry about merging to the portable mandoc
> > on mdocml.bsd.lv.  That's a no-brainer i'll take care of.
> >
> >> Can the results be sent incrementally?
> >
> > Yes, that's ideal.
> >
> > Don't work for days before sending anything.  Imagine you misunderstand
> > something and only learn about your error after having wasted days
> > of work.  That would be bad.  Or imagine two people start working
> > on the same task and work for days, both preparing the same huge
> > report.  That would be a waste, too.  That cannot happen if you
> > send results incrementally right after finding them.
>
> Sorry I'm late to the party, as usual, but I had some trouble getting
> my -current setup back to a reasonable state.  I would like to pitch
> in on this if it is still needed, and don't want to duplicate work.  I
> have a list of 221 hits for %s in /usr/src/usr.bin/mandoc in front of
> me.  Shall I start at the top or has that already happened?
>
> > In general, OpenBSD prefers small patches that are easy to understand
> > and verify, in particular from new contributors.  They need not be
> > easy to produce, though.
> >
> > Yours,
> >   Ingo
>
> Pax, -A
> --
> http://haqistan.net/~attila | [email protected] | 0x62A729CF

Reply via email to