unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Roman Scherer <roman.scherer@burningswell.com>
Cc: emacs-devel@gnu.org,  ahyatt@gmail.com
Subject: Re: Add plz-media-type and plz-event-source to GNU ELPA when stabilised
Date: Wed, 01 May 2024 11:56:28 +0000	[thread overview]
Message-ID: <87o79prbir.fsf@posteo.net> (raw)
In-Reply-To: <8734r14vuk.fsf@burningswell.com> (Roman Scherer's message of "Wed, 01 May 2024 13:25:55 +0200")

Roman Scherer <roman.scherer@burningswell.com> writes:

> Hi Philip,
>
> I splitted the README and the manual. I attached 2 new patches which I
> created from adding the packages to the elpa repository locally.
>
> I also declare the ignored files now in the .elpaignore file of the
> repositories.
>
> The tarballs now cintain this:
>
>  -rw-rw-r--   roman/roman     30814 plz-media-type-0.1pre0.20240501.111146/plz-media-type.el
>  -rw-rw-r--   roman/roman      1825 plz-media-type-0.1pre0.20240501.111146/README-elpa
>  -rw-rw-r--   roman/roman       429 plz-media-type-0.1pre0.20240501.111146/plz-media-type-pkg.el
>  -rw-rw-r--   roman/roman      1329 plz-media-type-0.1pre0.20240501.111146/README.org
>  -rw-rw-r--   roman/roman     19165 plz-media-type-0.1pre0.20240501.111146/plz-media-type.info
>
>  -rw-rw-r--   roman/roman      4390 plz-event-source-0.1pre0.20240501.111443/plz-event-source.info
>  -rw-rw-r--   roman/roman      1689 plz-event-source-0.1pre0.20240501.111443/README-elpa
>  -rw-rw-r--   roman/roman      1140 plz-event-source-0.1pre0.20240501.111443/README.org
>  -rw-rw-r--   roman/roman     18249 plz-event-source-0.1pre0.20240501.111443/plz-event-source.el
>  -rw-rw-r--   roman/roman       436 plz-event-source-0.1pre0.20240501.111443/plz-event-source-pkg.el
>
> Thanks, Roman.

Thank you, I have applied and pushed your patches to elpa.git (note that
I changed the message to conform with the usual commit style).  The
packages should appear on GNU ELPA a few hours after you update the
Version header as discussed before.

-- 
	Philip Kaludercic on peregrine



  reply	other threads:[~2024-05-01 11:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-27  9:02 Add plz-media-type and plz-event-source to GNU ELPA when stabilized Roman Scherer
2024-04-27 13:43 ` Philip Kaludercic
2024-04-28 12:56   ` Roman Scherer
2024-04-29  6:09     ` Philip Kaludercic
2024-04-29  7:44       ` Roman Scherer
2024-04-29  7:46         ` Philip Kaludercic
2024-04-29  7:48           ` Roman Scherer
2024-04-29 18:24             ` Add plz-media-type and plz-event-source to GNU ELPA when stabilised Philip Kaludercic
2024-04-29 20:17               ` Roman Scherer
2024-05-01 11:25               ` Roman Scherer
2024-05-01 11:56                 ` Philip Kaludercic [this message]
2024-05-01 12:00                   ` Roman Scherer

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o79prbir.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=ahyatt@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=roman.scherer@burningswell.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).