From: phillip.lord@russet.org.uk (Phillip Lord)
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-devel@gnu.org
Subject: Re: ELPA contributions?
Date: Tue, 13 Oct 2015 10:35:47 +0100 [thread overview]
Message-ID: <878u77t8jw.fsf@russet.org.uk> (raw)
In-Reply-To: <877fmrd8fg.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 12 Oct 2015 15:32:51 -0700")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>> All of this should really be better explained on the readme. I
>>> remember I felt a little lost the first time I was doing it. If anyone
>>> would like to document these steps a bit better I would be thoroughly
>>> grateful.
>>
>> I really regret squashing: I think I only did it because of some vague
>> sense that it would be more hygienic. Fairly nonsensical, but I don't
>> think it's possible, or practical, to unsquash at this point. For the
>> sake of simplicity, I think it would be good if the README recommends
>> not squashing.
If I understand, a git subtree squash is not like a normal rebase; it
does actually know about the commits that were squashed, as opposed to
rewriting them like a rebase squash.
> Also, Stefan's original recommendation was to just develop the package
> in ELPA: no remote.
>
> I think this could be a more viable option if debbugs integrated with
> ELPA a bit better. Personally, I wanted Github a tiny bit for the fame
> and the glory, but mostly because of the issue tracking. Other people
> probably make more use of Github's functionality (Phil mentioned pull
> requests, etc),
For my own packages, I'd moved them from mercurial on google code to
github shortly before, so shifting the development to ELPA didn't seem
like a good way forward. For dash, it just reflects the reality -- it
was already developed on github and wasn't going to move.
> but in my case, if I got an automatic email anytime anyone reported an
> Emacs bug with "gnorb" in the package header...
>
> Hang on, back up. If `report-emacs-bug' prompted the user for a package
> (with completion), and then I was automatically emailed with any bug
> reports filed against my package(s) (where I'm in the Maintainer
> header), and then I could continue that back-and-forth via debbugs, most
> of the allure of Github would be gone for me, and I'd probably just do
> the development within ELPA.
All of that would help.
Phil
next prev parent reply other threads:[~2015-10-13 9:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 8:32 ELPA contributions? David Kastrup
2015-10-09 22:42 ` Artur Malabarba
2015-10-10 6:55 ` David Kastrup
2015-10-10 7:00 ` David Kastrup
2015-10-10 22:24 ` Artur Malabarba
2015-10-10 22:26 ` Artur Malabarba
2015-10-12 12:44 ` Phillip Lord
2015-10-12 16:00 ` Eric Abrahamsen
2015-10-12 20:54 ` Phillip Lord
2015-10-12 21:54 ` Artur Malabarba
2015-10-13 9:27 ` Phillip Lord
2015-10-12 21:25 ` Artur Malabarba
2015-10-12 22:14 ` Eric Abrahamsen
2015-10-12 22:32 ` Eric Abrahamsen
2015-10-13 9:35 ` Phillip Lord [this message]
2015-10-13 11:30 ` Artur Malabarba
2015-10-13 17:38 ` Eric Abrahamsen
2015-10-14 11:14 ` Phillip Lord
2015-10-12 21:44 ` Artur Malabarba
2015-10-13 11:15 ` Phillip Lord
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=878u77t8jw.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
/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.