From: Andrew Tropin via Guix-patches via <guix-patches@gnu.org>
To: 67961@debbugs.gnu.org, 67961-done@debbugs.gnu.org
Cc: ngraves@ngraves.fr
Subject: [bug#67961] [PATCH 0/3] Rename and update emacs-org-agenda-files-track.
Date: Thu, 18 Jan 2024 11:03:00 +0300 [thread overview]
Message-ID: <87jzo7m5l7.fsf@trop.in> (raw)
In-Reply-To: <20231221221749.30979-1-ngraves@ngraves.fr>
[-- Attachment #1: Type: text/plain, Size: 738 bytes --]
On 2023-12-21 23:17, Nicolas Graves via Guix-patches via wrote:
> MELPA's maintainers advised for a rename before integration, hence the patch series.
>
> Nicolas Graves (3):
> gnu: emacs-org-dynamic-agenda: Rename package to
> emacs-org-agenda-files-track.
> gnu: emacs-org-dynamic-agenda-ql: Rename package to
> emacs-org-agenda-files-track-ql.
> gnu: emacs-org-agenda-files-track: Update to 0.4.0.
>
> gnu/packages/emacs-xyz.scm | 34 +++++++++++++++++++---------------
> 1 file changed, 19 insertions(+), 15 deletions(-)
Thank you! Applied, pushed. I screwed up an author name a bit, so it's
Nicolas Graves via Guix-patches via <guix-patches@gnu.org>, sorry :)
--
Best regards,
Andrew Tropin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2024-01-18 8:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 22:17 [bug#67961] [PATCH 0/3] Rename and update emacs-org-agenda-files-track Nicolas Graves via Guix-patches via
2023-12-21 22:26 ` [bug#67961] [PATCH 1/3] gnu: emacs-org-dynamic-agenda: Rename package to emacs-org-agenda-files-track Nicolas Graves via Guix-patches via
2023-12-21 22:27 ` [bug#67961] [PATCH 2/3] gnu: emacs-org-dynamic-agenda-ql: Rename package to emacs-org-agenda-files-track-ql Nicolas Graves via Guix-patches via
2023-12-21 22:27 ` [bug#67961] [PATCH 3/3] gnu: emacs-org-agenda-files-track: Update to 0.4.0 Nicolas Graves via Guix-patches via
2024-01-18 8:03 ` Andrew Tropin via Guix-patches via [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87jzo7m5l7.fsf@trop.in \
--to=guix-patches@gnu.org \
--cc=67961-done@debbugs.gnu.org \
--cc=67961@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=ngraves@ngraves.fr \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.