From: Lars Ingebrigtsen <larsi@gnus.org>
To: raman <raman@google.com>
Cc: John Wiegley <jwiegley@gmail.com>, Eli Zaretskii <eliz@gnu.org>,
deng@randomsample.de, emacs-devel@gnu.org
Subject: Re: EWW To Elpa? Re: Having a custom merge process
Date: Sat, 26 Dec 2015 18:51:43 +0100 [thread overview]
Message-ID: <87k2o1ksi8.fsf@gnus.org> (raw)
In-Reply-To: <p91poxtdu26.fsf_-_@google.com> (raman@google.com's message of "Sat, 26 Dec 2015 09:00:01 -0800")
raman <raman@google.com> writes:
> Given that EWW is a relatively stand-alone package, should it also be
> available via elpa -- in addition to being bundled?
No, that would make eww much more awkward to develop. Making a package
usable in one single environment (well, two with a release branch and
trunk) is way, way, way less work than making it work over a larger
range of environments.
> Asking specifically because recent fixes have only landed in Master --
> not the 25.1 branch, and at this point, there are things in 25.1 that
> are not in Master -- so even for those building from git@head, it's hard
> to get all the goodness in one build.
Well, the mergings from 25.1 to the trunk should happen more frequently
from now on, according to rumblings on this mailing list... :-)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2015-12-26 17:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-25 7:52 EWW bugs should be fixed on emacs-25 branch Eli Zaretskii
2015-12-25 8:06 ` Eli Zaretskii
2015-12-25 8:26 ` David Kastrup
2015-12-25 14:18 ` Eli Zaretskii
2015-12-25 16:58 ` John Wiegley
2015-12-25 17:15 ` Eli Zaretskii
2015-12-25 17:23 ` John Wiegley
2015-12-25 19:41 ` Eli Zaretskii
2015-12-25 19:55 ` John Wiegley
2015-12-25 20:00 ` Eli Zaretskii
2015-12-25 20:09 ` John Wiegley
2015-12-25 20:40 ` Eli Zaretskii
2015-12-25 20:44 ` John Wiegley
2015-12-25 20:48 ` Eli Zaretskii
2015-12-25 20:53 ` John Wiegley
2015-12-25 23:18 ` David Engster
2015-12-25 23:35 ` Having a custom merge process (was: EWW bugs should be fixed on emacs-25 branch) John Wiegley
2015-12-25 23:40 ` Having a custom merge process Lars Ingebrigtsen
2015-12-25 23:59 ` David Engster
2015-12-26 0:47 ` John Wiegley
2015-12-26 7:35 ` Paul Eggert
2015-12-26 9:47 ` Eli Zaretskii
2015-12-26 9:44 ` Having a custom merge process (was: EWW bugs should be fixed on emacs-25 branch) Eli Zaretskii
2015-12-26 17:00 ` EWW To Elpa? Re: Having a custom merge process raman
2015-12-26 17:51 ` Lars Ingebrigtsen [this message]
2015-12-26 21:06 ` Artur Malabarba
2015-12-28 21:17 ` John Wiegley
2015-12-26 18:40 ` Artur Malabarba
2015-12-27 16:29 ` raman
2015-12-27 2:52 ` Having a custom merge process (was: EWW bugs should be fixed on emacs-25 branch) Richard Stallman
2015-12-27 3:49 ` Eli Zaretskii
2015-12-25 16:07 ` EWW bugs should be fixed on emacs-25 branch Lars Ingebrigtsen
2015-12-25 16:21 ` 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
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=87k2o1ksi8.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=deng@randomsample.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@gmail.com \
--cc=raman@google.com \
/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).