From: Xue Fuqiao <xfq.free@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: David Kastrup <dak@gnu.org>, emacs-devel@gnu.org
Subject: Re: Licensing of NEWS files?
Date: Fri, 16 Oct 2015 07:00:22 +0800 [thread overview]
Message-ID: <CAAF+z6HXczzy3rOzJZkhrymV0bK4FfBX3t9r6tFEOMMNez2mLQ@mail.gmail.com> (raw)
In-Reply-To: <56202341.7060702@cs.ucla.edu>
On Fri, Oct 16, 2015 at 6:05 AM, Paul Eggert <eggert@cs.ucla.edu> wrote:
>> Granted, that did not annoy me as much for licensing reasons as
>> it did for making it unable to get a rough estimate when the various
>> major versions of Emacs had been released.
>
> Yes, I've also run afoul of that. I attempted to help out by installing the
> attached patch. Some of this is from my vague recollections, some from
> random places on the Internet, and quite possibly I've made transcription
> errors; corrections and improvements are welcome.
I think etc/RELEASES or etc/RELEASE-HISTORY are better names than
etc/HISTORY if the content of the file only contains release version
numbers/dates. IMO a file named HISTORY should be something like
these:
* https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/History.html#History
* https://www.gnu.org/software/texinfo/manual/texinfo/html_node/History.html#History
next prev parent reply other threads:[~2015-10-15 23:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 15:58 Licensing of NEWS files? David Kastrup
2015-10-15 16:13 ` Dmitry Gutov
2015-10-15 16:19 ` Marcin Borkowski
2015-10-15 16:32 ` Dmitry Gutov
2015-10-16 1:16 ` Stephen J. Turnbull
2015-10-15 16:34 ` David Kastrup
2015-10-15 16:31 ` Eli Zaretskii
2015-10-15 16:43 ` David Kastrup
2015-10-15 22:05 ` Paul Eggert
2015-10-15 23:00 ` Xue Fuqiao [this message]
2016-02-01 0:56 ` Paul Eggert
2016-02-01 3:16 ` Xue Fuqiao
2015-10-16 8:58 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAF+z6HXczzy3rOzJZkhrymV0bK4FfBX3t9r6tFEOMMNez2mLQ@mail.gmail.com \
--to=xfq.free@gmail.com \
--cc=dak@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.