From: Brett Gilio <brettg@posteo.net>
To: 34933@debbugs.gnu.org
Subject: [bug#34933] [PATCH] gnu: emacs-hackernews: Update to 0.5.0.
Date: Wed, 20 Mar 2019 21:22:50 -0500 [thread overview]
Message-ID: <87a7hpge4l.fsf@posteo.net> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: [PATCH] gnu: emacs-hackernews: Update to 0.5.0. --]
[-- Type: text/x-patch, Size: 1422 bytes --]
From 2b77fdfe69d2e1882f184a9f7ca24ad45ece3273 Mon Sep 17 00:00:00 2001
From: Brett Gilio <brettg@posteo.net>
Date: Wed, 20 Mar 2019 21:22:10 -0500
Subject: [PATCH] gnu: emacs-hackernews: Update to 0.5.0.
* gnu/packages/emacs-xyz.scm (emacs-hackernews): Update to 0.5.0.
---
gnu/packages/emacs-xyz.scm | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/gnu/packages/emacs-xyz.scm b/gnu/packages/emacs-xyz.scm
index 9969c7968..fdda71ac7 100644
--- a/gnu/packages/emacs-xyz.scm
+++ b/gnu/packages/emacs-xyz.scm
@@ -12407,10 +12407,10 @@ files) are provided.")
(license license:gpl2+))))
(define-public emacs-hackernews
- (let ((commit "d8c450bbc76d6bb65ec5cdb6c3b888a23f3769e9"))
+ (let ((commit "916c3da8da45c757f5ec2faeed57fa370513d4ac"))
(package
(name "emacs-hackernews")
- (version (git-version "0.4.0" "1" commit))
+ (version (git-version "0.5.0" "1" commit))
(source
(origin
(method git-fetch)
@@ -12420,7 +12420,7 @@ files) are provided.")
(file-name (git-file-name name version))
(sha256
(base32
- "06mp4n6c300jv5lhwf50ircfjckzr2p1zd38s4mqnxxjlf1maim7"))))
+ "09bxaaczana1cfvxyk9aagjvdszkj0j1yldl5r4xa60b59lxihsg"))))
(build-system emacs-build-system)
(home-page "https://github.com/clarete/hackernews.el")
(synopsis "Hacker News client for Emacs")
--
2.21.0
next reply other threads:[~2019-03-21 2:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 2:22 Brett Gilio [this message]
2019-03-21 8:35 ` bug#34933: [PATCH] gnu: emacs-hackernews: Update to 0.5.0 Ricardo Wurmus
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=87a7hpge4l.fsf@posteo.net \
--to=brettg@posteo.net \
--cc=34933@debbugs.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.
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.