|
From: | GNU bug Tracking System |
Subject: | [debbugs-tracker] bug#25541: closed ([PATCH] Some small bat-mode fixes) |
Date: | Fri, 10 Feb 2017 09:31:01 +0000 |
Your message dated Fri, 10 Feb 2017 11:30:08 +0200 with message-id <address@hidden> and subject line Re: bug#25541: [PATCH] Some small bat-mode fixes has caused the debbugs.gnu.org bug report #25541, regarding [PATCH] Some small bat-mode fixes to be marked as done. (If you believe you have received this mail in error, please contact address@hidden) -- 25541: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=25541 GNU Bug Tracking System Contact address@hidden with problems
--- Begin Message ---Subject: [PATCH] Some small bat-mode fixes Date: Thu, 26 Jan 2017 04:36:21 +0000 These fix a few issues with fontification and fill-paragraph in bat-mode (used for Windows .bat and .cmd files). Tests included.
--- End Message ---
--- Begin Message ---Subject: Re: bug#25541: [PATCH] Some small bat-mode fixes Date: Fri, 10 Feb 2017 11:30:08 +0200 > From: Vladimir Panteleev <address@hidden> > Date: Thu, 26 Jan 2017 04:36:21 +0000 > > These fix a few issues with fontification and fill-paragraph in > bat-mode (used for Windows .bat and .cmd files). Tests included. Thanks, pushed to the master branch. In the future, please make sure the commit log entries indicate the function in which each change was made. E.g., here: * lisp/progmodes/bat-mode.el: Set comment-start-skip. the function is bat-mode, so the log entry should have said * lisp/progmodes/bat-mode.el (bat-mode): Set comment-start-skip. You can use "C-x 4 a" to format the commit messages for you.
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |