From: Stephen Meister <pallagun@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Help adding a package to NonGNU Elpa
Date: Wed, 3 Nov 2021 10:57:35 -0400 [thread overview]
Message-ID: <CAMrh0GMkL0sR9Psq5Z0DsQuEey7qjYPrjejyY7YP7sWa7-B7fQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
> IIUC you're just seeing some error messages, but the command does do
> what you asked (i.e. the error messages are "noise" that you can
> ignore).
Yep, you're correct. I misunderstood that output.
I'm now at the point where the README
(https://git.savannah.gnu.org/cgit/emacs/nongnu.git/tree/README.org#n241)
tells me to git push which is failing because I don't have
permissions. I don't think I have such permissions so that makes
sense. I asked in the emacs IRC channel and the suggestion was to
mail the patch to the emacs-devel mailing list. Is this the correct
way to submit code? I don't mind mailing a patch but it's a process
I've never worked with before.
I've noted https://www.gnu.org/software/emacs/manual/html_node/emacs/Sending-Patches.html
as well, which suggests sending patches to the bug-gnu-emacs mailing
list. That list appears to only be applicable to existing bugs
though, which I don't currently have.
Any suggestions for how to continue? I've tried to attach my patch
here for reference.
-steve
[-- Attachment #2: 0001-elpa-packages-cpupower-New-package.patch --]
[-- Type: text/x-patch, Size: 774 bytes --]
From f3e158645ebfbd84c40c2610e6a22f86860c3bdd Mon Sep 17 00:00:00 2001
From: smeister <pallagun@gmail.com>
Date: Wed, 3 Nov 2021 08:16:29 -0400
Subject: [PATCH] * elpa-packages (cpupower): New package
---
elpa-packages | 3 +++
1 file changed, 3 insertions(+)
diff --git a/elpa-packages b/elpa-packages
index 0de123b1dc..4b0a2b1340 100644
--- a/elpa-packages
+++ b/elpa-packages
@@ -40,6 +40,9 @@
:ignored-files ("clojure-mode-extra-font-locking.el" "doc" "test" "test.clj")
:news "CHANGELOG.md")
+ ("cpupower" :url "https://gitlab.com/steve-emacs-stuff/cpupower-el.git"
+ :ignored-files ("README.md" "COPYING"))
+
("crux" :url "https://github.com/bbatsov/crux")
("cyberpunk-theme" :url "https://github.com/n3mo/cyberpunk-theme.el"
--
2.32.0
next reply other threads:[~2021-11-03 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 14:57 Stephen Meister [this message]
2021-11-03 19:01 ` Help adding a package to NonGNU Elpa Stefan Monnier via Users list for the GNU Emacs text editor
-- strict thread matches above, loose matches on Subject: below --
2021-11-02 20:57 Stephen Meister
2021-11-02 22:19 ` Stefan Monnier via Users list for the GNU Emacs text editor
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=CAMrh0GMkL0sR9Psq5Z0DsQuEey7qjYPrjejyY7YP7sWa7-B7fQ@mail.gmail.com \
--to=pallagun@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.
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).