bug-standards
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How much explanation to include in change descriptions


From: Richard Stallman
Subject: Re: How much explanation to include in change descriptions
Date: Tue, 16 Jan 2018 20:11:11 -0500

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  >  >    > Fix .gdbinit to work with Lisp_Word (Bug#29957)
  >  >
  >  > is unhelpfully terse: it makes people work harder to understand the 
change.

  > We could change the line to:

  > Fix .gdbinit when Lisp_Word is pointer (Bug#29957)

  > as this captures the detail that was missing in the too-terse version.

I agree that would be better.  But 

  > Cast Lisp_Word value to EMACS_INT, since it might be a pointer (Bug#29957)

seems even better.

-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
Skype: No way! See https://stallman.org/skype.html.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]