From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: tumashu <tumashu@163.com>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>,
Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: [RFC] Add posframe.el to elpa
Date: Tue, 27 Feb 2018 14:56:55 -0500 [thread overview]
Message-ID: <jwvr2p6rz0u.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <758b0884.7d7.161d498b671.Coremail.tumashu@163.com> (tumashu's message of "Tue, 27 Feb 2018 08:10:33 +0800 (CST)")
> At the moment , I have no write access of elpa.git. I am waiting for approval
> the request inclustion of elpa :-)
You should have access now.
And I just added your package with
git subtree add --prefix=packages/posframe posframe/master
Apparently it had already the right copyright header and compiled
without warnings, so you got two extra karma points today.
> By the way, including a package to elpa seem to be more complex than melpa.
Indeed.
GNU ELPA is not just a site to distribute packages, it's the site where
we distribute the packages hosted in elpa.git, which we want to be
a kind of "halfway" between MELPA and Emacs itself.
Stefan "who now sees that something went wrong in his git
subtree add. Darn!"
next prev parent reply other threads:[~2018-02-27 19:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 8:57 [RFC] Add posframe.el to elpa tumashu
2018-02-23 15:16 ` Stefan Monnier
2018-02-24 0:22 ` tumashu
2018-02-25 13:10 ` Stefan Monnier
2018-02-25 23:45 ` Feng Shu
2018-02-26 3:20 ` Stefan Monnier
2018-02-26 7:44 ` tumashu
2018-02-26 10:51 ` Dmitry Gutov
2018-02-27 0:10 ` tumashu
2018-02-27 19:56 ` Stefan Monnier [this message]
2018-02-28 2:21 ` tumashu
2018-02-28 2:42 ` Eric Abrahamsen
2018-02-28 5:48 ` tumashu
2018-02-28 2:43 ` Stefan Monnier
2018-02-28 5:42 ` tumashu
2018-02-28 14:56 ` Clément Pit-Claudel
2018-02-28 15:03 ` Kaushal Modi
2018-02-28 17:35 ` Richard Stallman
2018-02-28 17:59 ` Clément Pit-Claudel
2018-03-01 0:28 ` tumashu
2018-03-01 16:00 ` Richard Stallman
2018-03-01 16:20 ` Clément Pit-Claudel
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=jwvr2p6rz0u.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=tumashu@163.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).