Gnus development mailing list
 help / color / mirror / Atom feed
From: "Adam Sjøgren" <asjo@koldfront.dk>
To: ding@gnus.org
Subject: Re: Gnus version recent enough ?
Date: Wed, 04 May 2022 18:03:37 +0200	[thread overview]
Message-ID: <87sfppi8ti.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87bkwdnx06.fsf@ucl.ac.uk>

Eric writes:

> If gnus is now part of Emacs,

I think it has been almost from the beginning:

| The first "proper" release of Gnus 5 was done in November 1995 when it
| was included in the Emacs 19.30 distribution

  · https://www.gnus.org/history.html

In 2016 the development moved from it's own repository into Emacs'
repository - see the thread "Moving Gnus development to Emacs?" from the
end of 2015:

  · https://lists.gnu.org/archive/html/emacs-devel/2015-12/msg01511.html
  · https://lists.gnu.org/archive/html/emacs-devel/2016-01/msg00088.html

And:

  · https://lars.ingebrigtsen.no/2016/01/01/its-about-ethics-in-gnus-development/

> and its development and release coincide with Emacs's own, should it
> actually have a version number at all?

The version number hasn't reflected much since the independent
repository was closed.

Maybe add another digit for each Emacs release? 5.1333333.


  :-),

   Adam

-- 
 "Happiness isn't good enough for me! I demand              Adam Sjøgren
  euphoria!"                                           asjo@koldfront.dk



  reply	other threads:[~2022-05-04 16:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04 13:15 Erik Colson
2022-05-04 13:18 ` Robert Pluim
2022-05-04 13:31   ` Erik Colson
2022-05-04 14:16   ` Sam Steingold
2022-05-04 14:28     ` Robert Pluim
2022-05-04 15:22       ` Eric S Fraga
2022-05-04 16:03         ` Adam Sjøgren [this message]
2022-05-04 17:54           ` Eric S Fraga
2022-05-04 19:11         ` Sam Steingold
2022-05-04 19:20           ` Emanuel Berg
2022-05-05  8:03             ` Eric S Fraga
2022-05-05  4:19         ` Pankaj Jangid
2022-05-05 15:59           ` Andreas Schwab
2022-05-05 17:18             ` Sam Steingold
2022-05-06  3:11               ` Pankaj Jangid
2022-05-05 14:20         ` Sivaram Neelakantan

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=87sfppi8ti.fsf@tullinup.koldfront.dk \
    --to=asjo@koldfront.dk \
    --cc=ding@gnus.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 NNTP newsgroup(s).