From: Philip Kaludercic <philipk@posteo.net>
To: Yilkal Argaw <yilkalargawworkneh@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: add org-auto-tangle to NonGNU ELPA
Date: Tue, 07 Jun 2022 08:00:22 +0000 [thread overview]
Message-ID: <87ilpc9a3t.fsf@posteo.net> (raw)
In-Reply-To: <CAJddU=r5aw29q-pqKpN0zG3PeUEQ=Ug9ioCwJfBC9VyHEFTPRg@mail.gmail.com> (Yilkal Argaw's message of "Mon, 6 Jun 2022 20:56:14 +0300")
Yilkal Argaw <yilkalargawworkneh@gmail.com> writes:
>> I have applied and pushed the patch (with a reworded commit message).
>> Are you familiar with how ELPA works, e.g. how packages are updated?
>
> Not ELPA exactly but is it much different than MELPA?
Packages are synchronised daily, and the ELPA build system mirrors your
git repository. So you should watch out not to force-push commits,
otherwise the two might diverge.
New releases are created whenever a commit updates the ";; Version:" tag
in the package header. No special messages or Git tags are necessary.
And you should keep the NonGNU ELPA rules in mind:
https://git.savannah.gnu.org/cgit/emacs/nongnu.git/tree/README.org#n118
> On Mon, Jun 6, 2022 at 6:15 PM Philip Kaludercic <philipk@posteo.net> wrote:
>>
>>
>> >> > Ok here is a new patch.
>> >>
>> >> Ok, I can apply it if nobody objects.
>>
>> I have applied and pushed the patch (with a reworded commit message).
>> Are you familiar with how ELPA works, e.g. how packages are updated?
prev parent reply other threads:[~2022-06-07 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 4:52 add org-auto-tangle to NonGNU ELPA Yilkal Argaw
2022-06-03 7:54 ` Philip Kaludercic
[not found] ` <CAJddU=pSQ29bJg1bGzCHEqe99y4+DLHAPgP2ZSax40Cpah_ymw@mail.gmail.com>
[not found] ` <CAJddU=oB5e6d95Ggo-wGJefAbPCTse7wAciGn5Uf4mDp5eUfgA@mail.gmail.com>
[not found] ` <87ee063sx2.fsf@posteo.net>
2022-06-05 13:14 ` Yilkal Argaw
2022-06-05 14:13 ` Philip Kaludercic
2022-06-05 17:39 ` Yilkal Argaw
2022-06-06 15:15 ` Philip Kaludercic
2022-06-06 17:56 ` Yilkal Argaw
2022-06-07 8:00 ` Philip Kaludercic [this message]
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=87ilpc9a3t.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=yilkalargawworkneh@gmail.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.