From: "Drew Adams" <drew.adams@oracle.com>
To: "'Chong Yidong'" <cyd@gnu.org>
Cc: 13502-done@debbugs.gnu.org
Subject: bug#13502: 24.3.50; bad formatting in recent NEWS?
Date: Sat, 19 Jan 2013 20:37:01 -0800 [thread overview]
Message-ID: <89EBFDC27F2F4A4AA15AA324802C1347@us.oracle.com> (raw)
In-Reply-To: <87obgk8tip.fsf@gnu.org>
> > The longest is this one (87 chars):
> >
> > machine smtp.whatever.foo port 25 key "~/.my_smtp_tls.key" cert
> > "~/.my_smtp_tls.cert"
>
> It should be incredibly obvious why this line is an OK exception.
In spite of your hyperbole ("incredibly obvious", indeed), there is no need for
this line to be an exception. It is too long only because you have used
fictitious names that are too long. Those names do not explain anything, in any
case, and they need not be that long.
In addition, the text is incorrect. It is "incredibly obvious" that it is NOT
true that "you need to put" that line "in your ~/authinfo file instead." It is
no doubt 100% wrong that you should use that literal text. What should be said
is something like this:
If you had that set then you need to put
machine MACHINE port PORT key KEYFILE cert CERTFILE
where MACHINE is..., PORT is..., KEYFILE is..., and CERTFILE
is.... [Specification still missing.]
For example, MACHINE could be smtp.whatever.foo, PORT could
be 25, KEYFILE could be "~/.my_smtp_tls.key", and CERTFILE
could be "~/.my_smtp_tls.cert".
No long lines needed, and incorrect and misleading statement removed.
> As for any other lines, they will be cleaned up when it comes time to
> edit the NEWS file in preparation for the 24.4 pretest. No
> point filing a bug about this kind of thing.
Quite a pretension. What happened to such cleanup during the 24.3 pretest? Or
24.2? Same problems - same long lines even; no such cleanup.
> Closing.
Improvident.
prev parent reply other threads:[~2013-01-20 4:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 22:47 bug#13502: 24.3.50; bad formatting in recent NEWS? Drew Adams
2013-01-20 2:42 ` Chong Yidong
2013-01-20 4:37 ` Drew Adams [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=89EBFDC27F2F4A4AA15AA324802C1347@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=13502-done@debbugs.gnu.org \
--cc=cyd@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).