From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Thierry Volpiatto <thierry.volpiatto@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: company.el status?
Date: Fri, 08 Mar 2013 22:10:02 -0500 [thread overview]
Message-ID: <jwvr4jp5kyx.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87ip5384u5.fsf@gmail.com> (Thierry Volpiatto's message of "Thu, 07 Mar 2013 19:03:46 +0100")
> https://github.com/thierryvolpiatto/eldoc-eval.git
> https://github.com/thierryvolpiatto/ioccur.git
> And eldoc-eval is broken for 24.3+ on ELPA (Fixed on github).
There's no "ELPA" maintainer. So if the package's maintainer doesn't
want to maintain the ELPA version, that's what we get.
IOW, please keep the ELPA branch of your packages up-to-date.
Normally, you should be able to "bzr merge" from your github branch
(using the "bzr-git" plugin).
Stefan
next prev parent reply other threads:[~2013-03-09 3:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 17:37 company.el status? Dmitry Gutov
2013-03-07 18:03 ` Thierry Volpiatto
2013-03-07 20:50 ` Dmitry Gutov
2013-03-08 7:39 ` Thierry Volpiatto
2013-03-09 3:10 ` Stefan Monnier [this message]
2013-03-09 12:23 ` Thierry Volpiatto
2013-03-09 12:46 ` Xue Fuqiao
2013-03-09 13:38 ` Stefan Monnier
2013-03-09 14:59 ` Thierry Volpiatto
2013-03-09 15:50 ` Stefan Monnier
2013-03-07 18:27 ` Nikolaj Schumacher
2013-03-07 20:43 ` Dmitry Gutov
2013-03-08 11:17 ` Nikolaj Schumacher
2013-03-08 21:25 ` Dmitry Gutov
2013-03-08 22:52 ` Richard Stallman
2013-03-08 23:50 ` Dmitry Gutov
[not found] ` <B74660D8-9994-4E4C-A7C3-C1A1B9BD899A@mit.edu>
2013-03-09 0:11 ` Dmitry Gutov
2013-03-09 8:19 ` Eli Zaretskii
2013-03-27 2:56 ` Tim Cross
2013-03-27 3:28 ` Dmitry Gutov
2013-03-27 5:37 ` Stephen J. Turnbull
2013-03-10 1:15 ` Richard Stallman
2013-03-09 3:11 ` Stefan Monnier
2013-03-09 10:05 ` Dmitry Gutov
2013-03-09 13:38 ` Nikolaj Schumacher
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=jwvr4jp5kyx.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=thierry.volpiatto@gmail.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 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.