From: Soham Gumaste <sohamg2@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] New Package: p4_16-mode
Date: Fri, 17 Nov 2023 14:11:29 -0600 [thread overview]
Message-ID: <CAAr-Hh2XbekgZzjsKQuJxznMKXdnMhDSu2+-nHuUxirisAAb9w@mail.gmail.com> (raw)
In-Reply-To: <87edgoq1al.fsf@posteo.net>
> +;;; History:
> +
> +;; The headers above have no special meaning, and could also be
> +;; re-written in prose under a special section. Also, was the package
> +;; really created just a few days ago?
> +
I mean, moved the file into a repo of its own on that day, and began making some
modifications to better suit ELPA. The original file has a date from 2017.
Should I use that instead?
>
> I suppose you want to add the package to NonGNU ELPA then?
>
I was not familiar with the distinction between GNU ELPA and NonGNU
ELPA. But now
that I have read up a bit, NonGNU ELPA does fit better.
I have applied your patch, thanks for taking the time to help me with it.
Please let me know if any further changes are needed, or if I need to
create a new thread to submit to NonGNU ELPA.
Thanks
--
Soham Gumaste
sohamg2@gmail.com
next prev parent reply other threads:[~2023-11-17 20:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 20:31 [ELPA] New Package: p4_16-mode Soham Gumaste
2023-11-17 7:36 ` Philip Kaludercic
2023-11-17 20:11 ` Soham Gumaste [this message]
2023-11-18 21:12 ` Philip Kaludercic
2023-11-18 21:20 ` Soham Gumaste
2023-11-18 21:28 ` Soham Gumaste
2023-11-18 21:51 ` Philip Kaludercic
2023-11-18 22:18 ` Soham Gumaste
2023-11-20 18:09 ` Soham Gumaste
2023-11-23 5:57 ` Philip Kaludercic
-- strict thread matches above, loose matches on Subject: below --
2023-11-15 6:29 Pedro Andres Aranda Gutierrez
2023-11-15 17:23 ` Soham Gumaste
2023-11-23 20:06 ` sohamg2
2023-11-24 6:17 ` Pedro Andres Aranda Gutierrez
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=CAAr-Hh2XbekgZzjsKQuJxznMKXdnMhDSu2+-nHuUxirisAAb9w@mail.gmail.com \
--to=sohamg2@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).