From: Bruno Haible <bruno@clisp.org>
To: Asher Gordon <AsDaGo@posteo.net>
Cc: bug-gnulib@gnu.org
Subject: Re: Remove license modules
Date: Mon, 01 Jun 2020 20:00:03 +0200 [thread overview]
Message-ID: <2292820.SIrGmUdg9z@omega> (raw)
In-Reply-To: <87lflqqqo1.fsf@posteo.net>
Asher Gordon wrote on 2020-05-17:
> >> I also fixed a minor issue where "VCS" ended with
> >> "." rather than "@." (see (texinfo) Ending a Sentence).
> >
> > I won't spend time on a single instance of this very minor issue. But if
> > you want to submit a patch that fixes all instances of this issue, I'll
> > appreciate it.
>
> See the attached 0001-doc-Change-.-to-.-where-appropriate.patch. It
> turns out that there were quite a few instances that should be changed
Thanks. I've applied your patch, except for the changes to
maintain.texi
standards.texi
make-stds.texi
which I've forwarded to bug-standards.
We haven't been paying attention to this detail (write @. instead of .
to terminate a sentence that ends with an uppercase letter). Maybe
your patch will remind us to do it better in the future.
> Also, there were some '.'s that should be changed to '@.' in the license
> Texinfo files.
I don't know whom to contact to change these.
Bruno
next prev parent reply other threads:[~2020-06-01 18:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 17:51 Remove license modules Asher Gordon
2020-05-15 23:17 ` Bruno Haible
2020-05-16 18:03 ` Asher Gordon
2020-05-17 17:39 ` Bruno Haible
2020-05-17 19:58 ` Asher Gordon
2020-05-17 20:12 ` Asher Gordon
2020-06-01 18:00 ` Bruno Haible [this message]
2020-06-01 18:09 ` Paul Eggert
2020-06-01 19:06 ` Typographical errors in Texinfo format licenses Asher Gordon
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2292820.SIrGmUdg9z@omega \
--to=bruno@clisp.org \
--cc=AsDaGo@posteo.net \
--cc=bug-gnulib@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).