GNU bug report logs -
#34600
[PATCH 1/5] gnu: emacs-which-key: Update to 3.3.1.
Previous Next
Reported by: Brett Gilio <brettg <at> posteo.net>
Date: Thu, 21 Feb 2019 02:21:01 UTC
Severity: normal
Tags: patch
Done: iyzsong <at> member.fsf.org (宋文武)
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 34600 in the body.
You can then email your comments to 34600 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
guix-patches <at> gnu.org
:
bug#34600
; Package
guix-patches
.
(Thu, 21 Feb 2019 02:21:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Brett Gilio <brettg <at> posteo.net>
:
New bug report received and forwarded. Copy sent to
guix-patches <at> gnu.org
.
(Thu, 21 Feb 2019 02:21:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[0001-gnu-emacs-which-key-Update-to-3.3.1.patch (text/x-patch, inline)]
From f4ce2f1459ed5a3dc08094c03d98c4cc1eb91348 Mon Sep 17 00:00:00 2001
From: Brett Gilio <brettg <at> posteo.net>
Date: Wed, 20 Feb 2019 19:55:07 -0600
Subject: [PATCH 1/5] gnu: emacs-which-key: Update to 3.3.1.
* gnu/packages/emacs-xyz.scm (emacs-which-key): Update to 3.3.1.
---
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 cedc1efbc..80dc9eb63 100644
--- a/gnu/packages/emacs-xyz.scm
+++ b/gnu/packages/emacs-xyz.scm
@@ -7214,7 +7214,7 @@ or @code{treemacs}, but leveraging @code{Dired} to do the job of display.")
(define-public emacs-which-key
(package
(name "emacs-which-key")
- (version "3.3.0")
+ (version "3.3.1")
(source
(origin
(method url-fetch)
@@ -7223,7 +7223,7 @@ or @code{treemacs}, but leveraging @code{Dired} to do the job of display.")
version ".tar.gz"))
(sha256
(base32
- "1lsj314111cp2hjjwnv3f46ws1za6bm39rgy3l19044xf6a68j5w"))
+ "1g8k0js21bc8mlw6hvmg93zgfjhil77c30cv1hf85y4qb9ldvika"))
(file-name (string-append name "-" version ".tar.gz"))))
(build-system emacs-build-system)
(arguments
--
2.20.1
Information forwarded
to
guix-patches <at> gnu.org
:
bug#34600
; Package
guix-patches
.
(Thu, 21 Feb 2019 19:31:01 GMT)
Full text and
rfc822 format available.
Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Brett Gilio <brettg <at> posteo.net> skrev: (21 februari 2019 03:13:40 CET)
>
Hi Brett
You send a patch series without first sending an email to get a bug number.
We do this to keep series together under 1 number.
Could you try again and close these?
--
Sent from my k-9 mail for Android.
[Message part 2 (text/html, inline)]
Information forwarded
to
guix-patches <at> gnu.org
:
bug#34600
; Package
guix-patches
.
(Thu, 21 Feb 2019 19:31:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
guix-patches <at> gnu.org
:
bug#34600
; Package
guix-patches
.
(Thu, 21 Feb 2019 19:48:02 GMT)
Full text and
rfc822 format available.
Message #14 received at submit <at> debbugs.gnu.org (full text, mbox):
swedebugia writes:
> Brett Gilio <brettg <at> posteo.net> skrev: (21 februari 2019 03:13:40 CET)
>>
>
> Hi Brett
> You send a patch series without first sending an email to get a bug number.
> We do this to keep series together under 1 number.
>
> Could you try again and close these?
You're going to have to be more specific. Do all patch series go under a
single bug number?
Information forwarded
to
guix-patches <at> gnu.org
:
bug#34600
; Package
guix-patches
.
(Thu, 21 Feb 2019 19:48:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
guix-patches <at> gnu.org
:
bug#34600
; Package
guix-patches
.
(Thu, 21 Feb 2019 20:31:03 GMT)
Full text and
rfc822 format available.
Message #20 received at 34600 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On Thu, Feb 21, 2019 at 01:46:03PM -0600, Brett Gilio wrote:
> You're going to have to be more specific. Do all patch series go under a
> single bug number?
If the patches are related, or depend on each other, then they should be
mailed to the same bug number. Otherwise it's more difficult to review
the patches.
You can send an intro email to <guix-patches <at> gnu.org>, wait for the
number to be assigned, and then send the patches to that numbered
address <NNN <at> debbugs.gnu.org>.
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
guix-patches <at> gnu.org
:
bug#34600
; Package
guix-patches
.
(Thu, 21 Feb 2019 21:32:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 34600 <at> debbugs.gnu.org (full text, mbox):
Leo Famulari writes:
> On Thu, Feb 21, 2019 at 01:46:03PM -0600, Brett Gilio wrote:
>> You're going to have to be more specific. Do all patch series go under a
>> single bug number?
>
> If the patches are related, or depend on each other, then they should be
> mailed to the same bug number. Otherwise it's more difficult to review
> the patches.
>
> You can send an intro email to <guix-patches <at> gnu.org>, wait for the
> number to be assigned, and then send the patches to that numbered
> address <NNN <at> debbugs.gnu.org>.
Understood. Thank you, I will fix this asap.
Information forwarded
to
guix-patches <at> gnu.org
:
bug#34600
; Package
guix-patches
.
(Fri, 22 Feb 2019 13:47:01 GMT)
Full text and
rfc822 format available.
Message #26 received at 34600 <at> debbugs.gnu.org (full text, mbox):
On 02/21/2019 08:46 PM, Brett Gilio wrote:
> swedebugia writes:
>
>> Brett Gilio <brettg <at> posteo.net> skrev: (21 februari 2019 03:13:40 CET)
>> Hi Brett
>> You send a patch series without first sending an email to get a bug number.
>> We do this to keep series together under 1 number.
>>
>> Could you try again and close these?
> You're going to have to be more specific. Do all patch series go under a
> single bug number?
Sorry if I was unclear. Yes.
The details are here:
http://guix.info/manual/en/Submitting-Patches.html#Sending-a-Patch-Series
It was a bad idea to tell you to send them again, but it is nice to have
them together.
And thanks for the patches anyway :)
Reply sent
to
iyzsong <at> member.fsf.org (宋文武)
:
You have taken responsibility.
(Sun, 24 Feb 2019 03:11:03 GMT)
Full text and
rfc822 format available.
Notification sent
to
Brett Gilio <brettg <at> posteo.net>
:
bug acknowledged by developer.
(Sun, 24 Feb 2019 03:11:05 GMT)
Full text and
rfc822 format available.
Message #31 received at 34600-done <at> debbugs.gnu.org (full text, mbox):
Brett Gilio <brettg <at> posteo.net> writes:
>>From f4ce2f1459ed5a3dc08094c03d98c4cc1eb91348 Mon Sep 17 00:00:00 2001
> From: Brett Gilio <brettg <at> posteo.net>
> Date: Wed, 20 Feb 2019 19:55:07 -0600
> Subject: [PATCH 1/5] gnu: emacs-which-key: Update to 3.3.1.
Applied, thanks!
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sun, 24 Mar 2019 11:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 5 years and 28 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.