From: Matthew Carter <m@ahungry.com>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Does Elpa welcome themes? Or should those stay in Melpa?
Date: Tue, 27 Jan 2015 22:20:51 -0500 [thread overview]
Message-ID: <87fvavbnfw.fsf@ahungry.com> (raw)
In-Reply-To: <CAAdUY-LPj1=XgexL9JRsdF=J9iVhyFp1LQPxkRPU7LdS6OmRBA@mail.gmail.com> (Artur Malabarba's message of "Tue, 27 Jan 2015 23:19:44 -0200")
Artur Malabarba <bruce.connor.am@gmail.com> writes:
>> git subtree add --prefix packages/ahungry-theme \
>> https://github.com/ahungry/color-theme-ahungry master --squash
>>
>> And subsequent pulls via:
>>
>> git subtree pull --prefix packages/ahungry-theme \
>> https://github.com/ahungry/color-theme-ahungry master --squash
>
> This is what I do, but without the --squash. The squash hides all
> history for me, which is not what I want. It's ok for your package's
> history to be part of Gelpa's history.
>
Hi all,
I pushed ahungry-theme.el into GNU Elpa (Gelpa) as a subtree with the
squash option, as at one point I had some sample images of the theme in
the github repo, instead of hosted outside of it, and I didn't want to
fatten up the git history with old unused blob data (they are hosted
externally now and only referred to in the README.md).
Please let me know if there are any issues with the commit, and thanks
for letting me contribute to GNU Emacs/ELPA.
--
Matthew Carter (m@ahungry.com)
http://ahungry.com
next prev parent reply other threads:[~2015-01-28 3:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 19:56 Does Elpa welcome themes? Or should those stay in Melpa? M
2015-01-16 23:27 ` Stefan Monnier
2015-01-27 5:07 ` Matthew Carter
2015-01-27 17:34 ` Stefan Monnier
2015-01-27 23:27 ` Matthew Carter
2015-01-28 1:19 ` Artur Malabarba
2015-01-28 3:20 ` Matthew Carter [this message]
2015-01-28 3:53 ` Stefan Monnier
2015-01-16 23:41 ` Artur Malabarba
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=87fvavbnfw.fsf@ahungry.com \
--to=m@ahungry.com \
--cc=emacs-devel@gnu.org \
/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.