From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: A <a@redscript.org>, Ahmad Draidi <a.r.draidi@redscript.org>,
64657@debbugs.gnu.org
Cc: Andrew Tropin <andrew@trop.in>
Subject: [bug#64657] [PATCH] gnu: Add emacs-mu4e-dashboard.
Date: Sun, 16 Jul 2023 12:56:24 +0200 [thread overview]
Message-ID: <647d0bf96c571d4decc0f127cfd2a8f0cbfe9fc1.camel@gmail.com> (raw)
In-Reply-To: <7dac15b9-aad3-3175-bffe-e0a3dce4d392@redscript.org>
Am Sonntag, dem 16.07.2023 um 12:56 +0400 schrieb A:
> Hello,
>
> On 7/16/23 11:37, Liliana Marie Prikler wrote:
> > Am Sonntag, dem 16.07.2023 um 10:10 +0400 schrieb Ahmad Draidi:
> > > * gnu/packages/emacs-xyz.scm (emacs-mu4e-dashboard): New
> > > variable.
> > > ---
> > > gnu/packages/emacs-xyz.scm | 27 +++++++++++++++++++++++++++
> > > 1 file changed, 27 insertions(+)
> > >
> > > diff --git a/gnu/packages/emacs-xyz.scm b/gnu/packages/emacs-
> > > xyz.scm
> > > index 480096fb50..39e16da4cc 100644
> > > --- a/gnu/packages/emacs-xyz.scm
> > > +++ b/gnu/packages/emacs-xyz.scm
> > > @@ -26203,6 +26203,33 @@ (define-public emacs-mu4e-conversation
> > > maps the thread tree.")
> > > (license license:gpl3+))))
> > >
> > > +;; Package has no releases or tags. Version is extracted from
> > > "Version:"
> > > +;; keyword in main file.
> > > +(define-public emacs-mu4e-dashboard
> > > + (let ((commit "16ffbb2a36817647e345f60acdfaac66dda28c0f")
> > > + (revision "0"))
> > > + (package
> > > + (name "emacs-mu4e-dashboard")
> > > + (version (git-version "0.1.1" revision commit))
> > > + (source (origin
> > > + (method git-fetch)
> > > + (file-name (git-file-name name version))
> > > + (uri (git-reference
> > > + (url
> > > "https://github.com/rougier/mu4e-dashboard")
> > > + (commit commit)))
> > > + (sha256
> > > + (base32
> > > +
> > > "1fp2f9rvh20r3advbzcgm5vv2dzcyvy1618hfykbm6ac4wjscdll"))))
> > Please put the file-name below the uri next time. Also, I see you
> > submitting quite a number of patches for emacs packages; if
> > possible,
> > try to make topical series so that they can be reviewed in one go.
>
> Noted.
>
> Should I resend this and a couple of other patches I submitted with
> the file-name position change?
I already fixed them locally, they should go live next Sunday.
Cheers
prev parent reply other threads:[~2023-07-16 10:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 6:10 [bug#64657] [PATCH] gnu: Add emacs-mu4e-dashboard Ahmad Draidi via Guix-patches via
2023-07-16 7:37 ` Liliana Marie Prikler
2023-07-16 8:56 ` A via Guix-patches via
2023-07-16 10:56 ` Liliana Marie Prikler [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=647d0bf96c571d4decc0f127cfd2a8f0cbfe9fc1.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=64657@debbugs.gnu.org \
--cc=a.r.draidi@redscript.org \
--cc=a@redscript.org \
--cc=andrew@trop.in \
/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/guix.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).