unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Arthur Miller <arthur.miller@live.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org,  Phillip Lord <phillip.lord@newcastle.ac.uk>
Subject: Re: Elpa question: helping with maintainance of a package in Elpa
Date: Wed, 07 Feb 2024 14:16:30 +0100	[thread overview]
Message-ID: <DU2PR02MB10109FCB72113993FF6ED63DF96452@DU2PR02MB10109.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <87jznhttmu.fsf@posteo.net> (Philip Kaludercic's message of "Tue,  06 Feb 2024 17:00:41 +0000")

Philip Kaludercic <philipk@posteo.net> writes:

> Arthur Miller <arthur.miller@live.com> writes:
>
>> I am helping Phillip to maintain his pabbrev package. He has given me write
>> access to his repository on GH, and I was able to update the package with few
>> patches It is currently just a "facelift" to skip compiler warnings when
>> installing.
>>
>> Do I understand the information in readme file from Elpa repository correctly: I
>> don't have to do anything special more than just update Phillips repo for the
>> package on GH, since the Cron job uses that URL to update the package
>> automatically if the version is changed? Or do I need to do something more to
>> get the new version into Elpa too?
>
> The cron job will synchronise the mirror with the changes made on the GH
> repository.  Just note that to release a package, you'll have to bump
> the version tag (any commit changing the line with the version number
> should do).
>
>> Since this is just a minor release; not new features, no changes in usability it
>> does not have to have "announcement" on this list, or do you always announce?
>
> No, package updates are usually never announced on emacs-devel.

Thank you very much; this was exactly the info I needed!

I saw it auto-updated last night. Not that I meant to do it; should have
reversed version :-), but it is ok.



      parent reply	other threads:[~2024-02-07 13:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06 15:57 Elpa question: helping with maintainance of a package in Elpa Arthur Miller
2024-02-06 17:00 ` Philip Kaludercic
2024-02-06 17:17   ` chad
2024-02-06 17:24     ` Philip Kaludercic
2024-02-07 13:16     ` Arthur Miller
2024-02-07 13:16   ` Arthur Miller [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

  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=DU2PR02MB10109FCB72113993FF6ED63DF96452@DU2PR02MB10109.eurprd02.prod.outlook.com \
    --to=arthur.miller@live.com \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    --cc=phillip.lord@newcastle.ac.uk \
    /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).