From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: Gnus cleanup
Date: Sat, 13 Feb 2016 14:43:13 +1100 [thread overview]
Message-ID: <87oablff72.fsf@gnus.org> (raw)
In-Reply-To: <8737sxcn92.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sat, 13 Feb 2016 11:17:29 +0800")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Scratch that, the problem is that bum commit 9dc77e went into both
> master and emacs-25, but the reversion only went into emacs-25. I've
> switched to emacs-25, and everything's normal.
I've now reverted it on master, too. Could you check whether it works
for you now?
> I know this debate is still ongoing, but is there any consensus here
> about whether we should be using master or emacs-25?
master should be getting all fixes that emacs-25 is getting, too, but
(as in this case) there may be some lag. On the other hand, master gets
all the new stuff. So it's up to you. :-)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-02-13 3:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 4:13 Lars Ingebrigtsen
2016-02-09 8:35 ` Michael Albinus
2016-02-09 8:35 ` Eric S Fraga
2016-02-09 11:42 ` Malcolm Purvis
2016-02-09 15:30 ` Stefan Monnier
2016-02-09 23:08 ` Lars Ingebrigtsen
2016-02-10 0:50 ` Greg Troxel
2016-02-12 4:19 ` Lars Ingebrigtsen
2016-02-13 0:22 ` Frank Haun
2016-02-13 1:57 ` Eric Abrahamsen
2016-02-13 3:17 ` Eric Abrahamsen
2016-02-13 3:43 ` Lars Ingebrigtsen [this message]
2016-02-13 4:26 ` Eric Abrahamsen
2016-02-13 4:59 ` Lars Ingebrigtsen
2016-02-13 12:00 ` Frank Haun
2016-02-13 15:37 ` Richard Stallman
2016-02-14 2:35 ` Lars Ingebrigtsen
2016-02-14 3:13 ` Adam Sjøgren
2016-02-14 13:12 ` Frank Haun
2016-02-17 21:10 ` Frank Haun
2016-02-18 12:29 ` Frank Haun
2016-03-07 13:52 ` Ted Zlatanov
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=87oablff72.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.org \
--cc=eric@ericabrahamsen.net \
/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).