GNU bug report logs - #25939
[PATCH] gnu: neomutt: Configure with "kyotocabinet".

Previous Next

Package: guix-patches;

Reported by: contact.ng0 <at> cryptolab.net

Date: Thu, 2 Mar 2017 21:13:01 UTC

Severity: normal

Tags: patch

Done: ng0 <contact.ng0 <at> cryptolab.net>

Bug is archived. No further changes may be made.

Full log


Message #25 received at 25939-done <at> debbugs.gnu.org (full text, mbox):

From: ng0 <contact.ng0 <at> cryptolab.net>
To: Kei Kebreau <kei <at> openmailbox.org>
Cc: 25939-done <at> debbugs.gnu.org, Leo Famulari <leo <at> famulari.name>
Subject: Re: bug#25939: Acknowledgement ([PATCH] gnu: neomutt: Configure with
 "kyotocabinet".)
Date: Fri, 17 Mar 2017 17:45:52 +0000
Kei Kebreau transcribed 2.3K bytes:
> ng0 <contact.ng0 <at> cryptolab.net> writes:
> 
> > On 17-03-02 17:01:36, Leo Famulari wrote:
> >> On Thu, Mar 02, 2017 at 09:31:54PM +0000, ng0 wrote:
> >> > In the last patch which added tokyocabinet and its support to neomutt, I
> >> > did not know that neomutt has support for kyotocabinet which is a
> >> > separate database from tokyocabinet but kyotocabinet is the currently
> >> > developed/recommended database (by the database upstream).
> >> > 
> >> > Should we add this in addition or drop tokyocabinet in favor of adding
> >> > kyotocabinet ? I'm okay with just adding it.
> >> 
> >> Sorry, I replied to the patch before seeing this message. If
> >> tokyocabinet is unmaintained or superseded by kyotocabinet, then let's
> >> just remove it from neomutt.
> >> 
> >> 
> >> 
> >
> > No problem, I've only realized it after the patch was merged in. After
> > all the patch includes not only the tokyodb.
> > I'd read the database website and leave it up to someone else as a
> > second opinion what's the best course of action here.
> > I only knew of kyotocabinet before I found tokyo and read as tokyo as
> > the work which happened before kyotocabinet.
> 
> FYI, I committed the patch a little while ago. I decided to remove
> tokyocabinet, as kyotocabinet seems to be its successor. You may close
> the bug if you feel it has been addressed satisfactorily.


I noticed it (thanks :) ). I just did not know this was still open. I
think you may close bugs (NNNNN-close <at> debbugs.gnu.org) after you have
pushed them. If there are questions, they can still be addressed in the
closed bug and reopened.




This bug report was last modified 8 years and 72 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.