|
From: | GNU bug Tracking System |
Subject: | bug#56393: closed (Actually fix the long lines display bug) |
Date: | Thu, 21 Jul 2022 11:57:02 +0000 |
Your message dated Thu, 21 Jul 2022 11:56:18 +0000 with message-id <b7551196d5a7dcdfe5ba@heytings.org> and subject line Re: bug#56393: Actually fix the long lines display bug has caused the debbugs.gnu.org bug report #56393, regarding Actually fix the long lines display bug to be marked as done. (If you believe you have received this mail in error, please contact help-debbugs@gnu.org.) -- 56393: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56393 GNU Bug Tracking System Contact help-debbugs@gnu.org with problems
--- Begin Message ---Subject: Actually fix the long lines display bug Date: Tue, 05 Jul 2022 08:49:30 +0000 Please review.Actually-fix-the-long-lines-display-bug.patch
Description: Text Data
--- End Message ---
--- Begin Message ---Subject: Re: bug#56393: Actually fix the long lines display bug Date: Thu, 21 Jul 2022 11:56:18 +0000 Okay. Should I wait for Lars' feedback?Merging into master is fine by me.Thanks, now done. Should I delete the feature branch? I don't remember what the policy is.
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |