From: Robert Pluim <rpluim@gmail.com>
To: "Bruno Félix Rezende Ribeiro" <oitofelix@gnu.org>
Cc: narendraj9@gmail.com, Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Patch for a simple nil check in `calc-graph-add-curve'
Date: Fri, 10 Apr 2020 16:31:28 +0200 [thread overview]
Message-ID: <m2h7xrqunz.fsf@gmail.com> (raw)
In-Reply-To: <87imi7h1tn.fsf@oitofelix.com> ("Bruno Félix Rezende Ribeiro"'s message of "Fri, 10 Apr 2020 11:07:00 -0300")
>>>>> On Fri, 10 Apr 2020 11:07:00 -0300, Bruno Félix Rezende Ribeiro <oitofelix@gnu.org> said:
Bruno> Eli Zaretskii <eliz@gnu.org> writes:
>>> From: Bruno Félix Rezende Ribeiro <oitofelix@gnu.org>
>>> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
>>> Date: Wed, 08 Apr 2020 11:47:53 -0300
>>> FWIW, this has /not/ been integrated into master yet.
>> It hasn't? I though that was bug#40155, already fixed.
Bruno> Sorry for the noise, then. Clearly my heuristics for deciding if
Bruno> something has been integrated into master is not good enough. I have to
Bruno> put GNU debbugs in the loop. Any other general hints on how to decide
Bruno> whether some report has been addressed?
When fixing a bug, the bug number should be in the commit
message. There should be no need to involve debbugs unless multiple
reports have been merged (and perhaps in that case the commit message
should mention all of them, although thatʼs not something Iʼve been
doing).
git log --grep [Bb]ug#40155
=>
commit c2b8ce4439935e2e158d4357d234135a251c5767
Author: Mattias Engdegård <mattiase@acm.org>
Date: Fri Mar 27 18:11:18 2020 +0100
Calc: don't treat nil as an integer (bug#40155)
Robert
next prev parent reply other threads:[~2020-04-10 14:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 19:48 Patch for a simple nil check in `calc-graph-add-curve' Narendra Joshi
2020-03-21 20:27 ` Eli Zaretskii
2020-03-21 21:56 ` Narendra Joshi
2020-04-08 14:47 ` Bruno Félix Rezende Ribeiro
2020-04-08 15:10 ` Eli Zaretskii
2020-04-08 15:27 ` Narendra Joshi
2020-04-10 14:07 ` Bruno Félix Rezende Ribeiro
2020-04-10 14:31 ` Robert Pluim [this message]
2020-04-10 15:33 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2h7xrqunz.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=narendraj9@gmail.com \
--cc=oitofelix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).