From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-devel@gnu.org
Subject: Re: ELPA contributions?
Date: Tue, 13 Oct 2015 10:38:35 -0700 [thread overview]
Message-ID: <87h9luactg.fsf@ericabrahamsen.net> (raw)
In-Reply-To: CAAdUY-JAZb6X9GrD_jfk-h6_hGm5Z-Byngc174hMhFior4xw2A@mail.gmail.com
Artur Malabarba <bruce.connor.am@gmail.com> writes:
> 2015-10-13 10:35 GMT+01:00 Phillip Lord <phillip.lord@russet.org.uk>:
>>
>> 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.
>
> Perhaps. But still, people should not squash to elpa.git. It has
> downsides with no real benefits (that I know of).
>
> - If your package is part of elpa.git, then its commit messages should
> be part of elpa.git's commit messages (even if the package is being
> primarily developed somewhere else).
> - The build-scripts can generate package change-logs from commit messages.
> - If someone is trying to `git-blame' one of your package files,
> having squashed is only going to complicate matters.
>
> I've added some better instructions to the Readme, but there's still
> much that needs to be done to it.
>
>> > 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.
>
> All agreed. Some packages are always going to prefer being primarily
> on Github. But having a better bug-tracker here would make it so that
> fewer packages feel obligated to be on Github. For let-alist, for
> instance, I wanted to develop the package here directly, so I created
> a github repo with no source just for the issue tracker..
Who runs debbugs? How hard would it be to add a cc based on the
Maintainer header?
next prev parent reply other threads:[~2015-10-13 17:38 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
2015-10-13 11:30 ` Artur Malabarba
2015-10-13 17:38 ` Eric Abrahamsen [this message]
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=87h9luactg.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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.