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:10 -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. ]]]

  > > It is useful to include a reference to the bug data base.
  > > But don't omit anything on the assumption that people have access to
  > > that data base.

  > That's asking for too much, and in practice developers typically don't do 
what's 
  > being asked for. Many bug reports are complex, and one must read them 
carefully 
  > to understand the bugs. We can't reasonably ask developers to write and 
read 
  > commit messages containing every detail of every report of a bug that was 
fixed. 
  > On the contrary: the GNU bug database is a useful tool for simplifying 
  > maintenance, and we should take advantage of it when that is a win.

I don't follow the response -- I have a feeling we are
miscommunicating somehow.

-- 
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]