GNU bug report logs - #37451
[PATCH] Update libvterm to version 0.1.1

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Ricardo Wurmus <rekado <at> elephly.net>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#37451: closed ([PATCH] Update libvterm to version 0.1.1)
Date: Wed, 18 Sep 2019 21:43:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Wed, 18 Sep 2019 23:42:07 +0200
with message-id <87imppnuxc.fsf <at> elephly.net>
and subject line Re: [bug#37451] [PATCH] Update libvterm to version 0.1.1
has caused the debbugs.gnu.org bug report #37451,
regarding [PATCH] Update libvterm to version 0.1.1
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
37451: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=37451
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: HiPhish <hiphish <at> posteo.de>
To: guix-patches <at> gnu.org
Subject: [PATCH] Update libvterm to version 0.1.1
Date: Wed, 18 Sep 2019 21:40:57 +0200

[Message part 3 (text/plain, inline)]

This patch bumps the version number of libvterm. The tarball for release 0.1 
has a bug which breaks the terminal emulator inside Neovim, so this new 
release fixes Neovim as well in the process.

[guix-libvterm.txt (text/plain, attachment)]

[Message part 5 (message/rfc822, inline)]

From: Ricardo Wurmus <rekado <at> elephly.net>
To: HiPhish <hiphish <at> posteo.de>
Cc: 37451-done <at> debbugs.gnu.org
Subject: Re: [bug#37451] [PATCH] Update libvterm to version 0.1.1
Date: Wed, 18 Sep 2019 23:42:07 +0200

Ricardo Wurmus <rekado <at> elephly.net> writes:

> Hi HiPhish,
>
>> This patch bumps the version number of libvterm. The tarball for release 0.1
>> has a bug which breaks the terminal emulator inside Neovim, so this new
>> release fixes Neovim as well in the process.
>
> thank you for this diff!
>
> I’d like to attribute this patch to you, but you’ve sent a diff (not the
> output of “git format-patch -1” after a commit) which doesn’t contain
> authorship information.  I would write a commit summary according to our
> conventions, but I’d need to know with what name and email address you
> would like to appear as the author.

Thanks for sending me the output of “git format-patch” off-list.  It
wasn’t *quite* the format I expected, so I made a few minor changes to
the commit message and pushed it to the master branch (see commit
b48d77fcf6).

Oh, before that I re-enabled the tests, because they work now.  Yay!

Thanks again!

--
Ricardo

Previous Next

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