unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Xiyue Deng <manphiz@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Where to send patches for ELPA packages
Date: Sun, 28 Jul 2024 15:20:02 -0700	[thread overview]
Message-ID: <877cd59n1p.fsf@debian-hx90.lan> (raw)
In-Reply-To: <871q3dtd76.fsf@posteo.net> (Philip Kaludercic's message of "Sun,  28 Jul 2024 21:32:29 +0000")

Hi Philip,

Philip Kaludercic <philipk@posteo.net> writes:

> Xiyue Deng <manphiz@gmail.com> writes:
>
>> Hi,
>>
>> I have been working on getting oauth2.el to work and have a few patches
>> that I think may improve its usability.  I'm aware of `send-emacs-bug',
>> but wondering whether that is the correct place to send patches for ELPA
>> packages?  Or is there another place for patches for ELPA packages?
>
> If you use package-vc, there is also `package-vc-prepare-patch', but
> that just uses the "Maintainer" address.  If the maintainer doesn't
> respond, you can send the patches to this mailing list and they can be
> pushed to elpa.git.  Note that this is a lot easier of the package is
> developed in elpa.git, not mirrored from some remote repository.
>

Thanks for the suggestions!  I have followed Emanuel's suggestion and
mailed the packages to the maintainer.  If I don't hear back in a few
days I'll forward the patches here.

>> Thanks in advance.

-- 
Xiyue Deng



  reply	other threads:[~2024-07-28 22:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-28 13:03 Where to send patches for ELPA packages Xiyue Deng
2024-07-28 17:05 ` Emanuel Berg
2024-07-28 19:34   ` Xiyue Deng
2024-07-28 21:32 ` Philip Kaludercic
2024-07-28 22:20   ` Xiyue Deng [this message]
2024-07-30  8:37     ` Xiyue Deng

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=877cd59n1p.fsf@debian-hx90.lan \
    --to=manphiz@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.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 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).