From: Brian Leung <bkleung89@gmail.com>
To: 35027@debbugs.gnu.org
Subject: [bug#35027] [PATCH] Update emacs-dired-hacks
Date: Thu, 28 Mar 2019 04:02:34 +0100 [thread overview]
Message-ID: <CAAc=MEx2bx_BMnOQHpf7g5-dZp=vysJKYoMwYXdh6=OgRc_gjg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 14 bytes --]
See attached.
[-- Attachment #1.2: Type: text/html, Size: 39 bytes --]
[-- Attachment #2: 0001-gnu-emacs-dired-hacks-Update-to-0.0.1-1.2c12345.patch --]
[-- Type: text/x-patch, Size: 1323 bytes --]
From e48d3ab188fde53998bd87dd0ba5b25fb5a438a3 Mon Sep 17 00:00:00 2001
From: Brian Leung <bkleung89@gmail.com>
Date: Thu, 28 Mar 2019 03:59:34 +0100
Subject: [PATCH] gnu: emacs-dired-hacks: Update to 0.0.1-1.2c12345.
* gnu/packages/emacs-xyz.scm (emacs-dired-hacks): Update to 0.0.1-1.2c12345.
---
gnu/packages/emacs-xyz.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/emacs-xyz.scm b/gnu/packages/emacs-xyz.scm
index 7554b02599..79b0c6d75d 100644
--- a/gnu/packages/emacs-xyz.scm
+++ b/gnu/packages/emacs-xyz.scm
@@ -7460,7 +7460,7 @@ the actual transformations.")
(license license:gpl2+))))
(define-public emacs-dired-hacks
- (let ((commit "eda68006ce73bbf6b9b995bfd70d08bec8cade36")
+ (let ((commit "2c1234592aee91dcd9401bcd67213e6a4a464fd9")
(revision "1"))
(package
(name "emacs-dired-hacks")
@@ -7474,7 +7474,7 @@ the actual transformations.")
(file-name (string-append name "-" version "-checkout"))
(sha256
(base32
- "1w7ssl9zssn5rcha6apf4h8drkd02k4xgvs203bdbqyqp9wz9brx"))))
+ "1g7mky41cahpryzj6frdgzdymknpqq7pidzfjj9304887kijmhj3"))))
(build-system emacs-build-system)
(propagated-inputs
`(("emacs-dash" ,emacs-dash)
--
2.21.0
next reply other threads:[~2019-03-28 3:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 3:02 Brian Leung [this message]
2019-03-28 18:16 ` bug#35027: [PATCH] Update emacs-dired-hacks Oleg Pykhalov
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='CAAc=MEx2bx_BMnOQHpf7g5-dZp=vysJKYoMwYXdh6=OgRc_gjg@mail.gmail.com' \
--to=bkleung89@gmail.com \
--cc=35027@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 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).