unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: Emacs developers <emacs-devel@gnu.org>, Juri Linkov <juri@linkov.net>
Subject: Re: Organizing the NEWS file a bit better
Date: Mon, 06 Sep 2021 11:04:24 +0200	[thread overview]
Message-ID: <87ilzejcrr.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkm=hubhEO6HzDvF3oMusw47NO3Jj2VKPsG-C9A3aQ_OW+Q@mail.gmail.com> (Stefan Kangas's message of "Mon, 6 Sep 2021 11:01:04 +0200")

Stefan Kangas <stefan@marxist.se> writes:

> The command 'org-set-tags-command' lines them up like this, which
> helps improve readability:
>
> ** 'open-gnutls-stream' now also accepts a ':coding' argument.          :DOC:
> ** 'process-attributes' now works under OpenBSD, too.                 :NODOC:

We try to limit the headings to below 80 characters...  which typically
means that a lot of them are almost exactly 80 characters.  :-)  So
these tags will make the NEWS file less readable.

The nice thing about having the tags on separate lines is that they
disappear from the VC history.  If we're changing the lines when we do
tagging, then it makes VC archaeology less convenient.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2021-09-06  9:04 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-04 18:53 Organizing the NEWS file a bit better Stefan Kangas
2021-09-04 19:04 ` Lars Ingebrigtsen
2021-09-04 19:34   ` Stefan Kangas
2021-09-04 19:47     ` Eli Zaretskii
2021-09-04 20:36   ` Tim Cross
2021-09-04 21:08     ` Stefan Kangas
2021-09-06  2:30   ` Stefan Kangas
2021-09-06  3:45     ` Jean-Christophe Helary
2021-09-06  6:35     ` Juri Linkov
2021-09-06  6:57       ` Stefan Kangas
2021-09-06  8:37         ` Lars Ingebrigtsen
2021-09-06  9:01           ` Stefan Kangas
2021-09-06  9:04             ` Lars Ingebrigtsen [this message]
2021-09-06 18:17               ` Stefan Kangas
2021-09-06 18:42                 ` Eli Zaretskii
2021-09-06 18:57                   ` Stefan Kangas
2021-09-06 19:18                     ` Eli Zaretskii
2021-09-06 20:38                       ` Stefan Kangas
2021-09-06 20:42                         ` Stefan Kangas
2021-09-07  5:38                         ` Eli Zaretskii
2021-09-07  6:47                           ` Stefan Kangas
2021-09-07  6:53                             ` Stefan Kangas
2021-09-07  8:12                             ` Eli Zaretskii
2021-09-07 15:09                     ` Lars Ingebrigtsen
2021-09-06 11:01             ` Eli Zaretskii
2021-09-06 11:07               ` Lars Ingebrigtsen
2021-09-06 11:20                 ` Eli Zaretskii
2021-09-06 10:39         ` Eli Zaretskii
2021-09-06 10:14     ` Eli Zaretskii
2021-09-04 19:05 ` Juri Linkov
2021-09-04 19:16 ` Eli Zaretskii
2021-09-04 19:35   ` Stefan Kangas

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=87ilzejcrr.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --cc=stefan@marxist.se \
    /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).