Gnus development mailing list
 help / color / mirror / Atom feed
From: Manuel Carro <manuel.carro@imdea.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ding-announce@gnus.org,  ding@gnus.org,  yamaoka@jpl.org
Subject: Re: Ma Gnus v0.16 is released
Date: Sun, 07 Feb 2016 01:15:28 +0100	[thread overview]
Message-ID: <871t8pfk9r.fsf@imdea.org> (raw)
In-Reply-To: <87zivejxkk.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 06 Feb 2016 15:09:59 +1100")


While building emacs is quite easy these days, I am not sure I want to
build new versions of all the Emacs packages when I get a new version of
gnus.  The possibility of new bugs increases a lot.  Won't it be
possible to mirror just the gnus directory and build it outside the
emacs sources?

Thanks!

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Gnus development has mainly been taking place externally for the last,
> er, 22 years?  But it's now moving to the Emacs code repository, as
> explained here:
>
> http://lars.ingebrigtsen.no/2016/01/01/its-about-ethics-in-gnus-development/

-- 
: Manuel Carro                              : manuel.carro@imdea.org     :
: Deputy director, IMDEA Software Institute : http://software.imdea.org  :
: Associate Professor, School of CS, UPM    : http://www.fi.upm.es       :
: EIT Digital Madrid                        : http://www.eitdigital.eu   :
: Madrid, Spain                             : +34-91-101-2202 ext. 4140  :



  parent reply	other threads:[~2016-02-07  0:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-06  4:09 Lars Ingebrigtsen
2016-02-06  8:09 ` Sivaram Neelakantan
2016-02-06 12:24 ` Bjørn Mork
2016-02-07  0:15 ` Manuel Carro [this message]
2016-02-07  2:47   ` Lars Ingebrigtsen
2016-02-07 16:07     ` Dave Abrahams

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=871t8pfk9r.fsf@imdea.org \
    --to=manuel.carro@imdea.org \
    --cc=ding-announce@gnus.org \
    --cc=ding@gnus.org \
    --cc=larsi@gnus.org \
    --cc=yamaoka@jpl.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).