Jim Meyering wrote:
> Pádraig Brady <[EMAIL PROTECTED]> wrote:
>> I also did a non user visible change to the info docs while I was
>> at it to standardize on using lower-case @var{file}:
>>
>> http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=1ce9d86c308d7daa6271a2e87629984b153ee9da
>
> Thanks!
> For a general policy-related change like that, I like
> to add a rule so that "make check" enforces it, so I've made
> the following change. Note that it uncovered a few more.
> It was a little tricky to automatically catch the cases in which
> there were two @var{...} uses on a single line and the first one was ok.
> There were two of those.
cool thanks (I was thinking about doing that myself :))
Note that I broke `make check` with my --files0-from doc checkin,
as I added NUL rather than @sc{nul} to coreutils.texi.
Note `make check` took about 2 hours due to the very slow msgmerge,
and I checked in anyway as I thought I couldn't break anything
with a simple doc emhancement :)
I'll fix this up ASAP.
cheers,
Pádraig.
_______________________________________________
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
