From: Nikolaj Schumacher <me@nschum.de>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Eli Zaretskii <eliz@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: company.el status?
Date: Sat, 09 Mar 2013 14:38:10 +0100 [thread overview]
Message-ID: <513B3B42.9000300@nschum.de> (raw)
In-Reply-To: <513B094D.5040204@yandex.ru>
On 2013-03-09 11:05, Dmitry Gutov wrote:
> On 09.03.2013 7:11, Stefan Monnier wrote:
>> Much better would be to use the ELPA branch as the official upstream.
> Leaving aside other details, I'd be more comfortable using ELPA for
> development if it were using Git (this is coming, I hear), and if it
> didn't lump all packages together in one repository.
> The current situation only seems useful when someone is making
> sweeping changes across packages, like updating copyright dates. This
> action seems to be relatively rare, and could be automated either way.
As I indicated, I haven't kept up with development and therefore know
very little about the current ELPA process.
It always seemed sensible to me to have a (public) development
repository and then push stable releases upstream.
From what Dmitry says, it doesn't sound like ELPA works as an easily
findable and forkable development repository.
> On 09.03.2013 12:19, Eli Zaretskii wrote:
> > Why do we need Github?
I've used it as such a development repository (to mirror my private
development)
Also, I suppose there should be some kind of project homepage.
I see a certain need for both these things, not for GitHub per se.
> The decision is up to Nikolaj, but for one thing, I expect strong
> correlation between people who prefer using completion mechanism with
> graphical interface and ones who would prefer a bug tracker with an
> actual user interface versus email-driven austerity that is Debbugs.
Actually, I'd like to leave this to you, Dmitry.
Since I'm not going to do much of the development work, I certainly
don't want to dictate the process. I'll support whatever works best for you.
kind regards,
Nikolaj Schumacher
prev parent reply other threads:[~2013-03-09 13:38 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
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 [this message]
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=513B3B42.9000300@nschum.de \
--to=me@nschum.de \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.