From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: tumashu <tumashu@163.com>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>,
Stefan Monnier <monnier@IRO.UMontreal.CA>,
Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: [RFC] Add posframe.el to elpa
Date: Tue, 27 Feb 2018 18:42:27 -0800 [thread overview]
Message-ID: <87efl5n8bw.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <368fc322.2db8.161da373f47.Coremail.tumashu@163.com> (tumashu's message of "Wed, 28 Feb 2018 10:21:49 +0800 (CST)")
tumashu <tumashu@163.com> writes:
> Thanks for the help :-)
>
>>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.
>
> I agree this, but I think the elpa.git's README is not enough for a new
> contributer who is first contribute to elpa.git.
FWIW, I found `git subtree` highly confusing, and hated using it. If you
intend to maintain your package repository both in ELPA and somewhere
else concurrently, I've found doing an "external" to be much easier to
handle.
2¢,
Eric
next prev parent reply other threads:[~2018-02-28 2:42 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
2018-02-28 2:21 ` tumashu
2018-02-28 2:42 ` Eric Abrahamsen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87efl5n8bw.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--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 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.