[Interest] PostgreSQL cross compile for Pi

[Roland Hughes]

If YOU need a copy of something which clearly will not fit within the 
confines of the bug tracker system YOU take the additional time to copy it.

Turning your argument around, what happens when your current bug 
tracking system disappears and is replaced by something else? You 
_still_ lose the history.

A deep bug history is only necessary when bugs are allowed to rot for 
decades. All actual changes must be accompanied by comments with the bug 
fix so the source code keeps its own history.


On 10/10/2017 01:45 AM, interest-request at qt-project.org wrote:
>> While we are on the topic, here is the lovely response.
>>
>> http://www.logikalsolutions.com/wordpress/wp-content/uploads/2017/10/Screenshot_20171009_143236.png
>>
>> No Sir By God! Not gonna look at a blog post with screen shots and
>> everything in it. Wants it cut & pasted into a text only box.
> There is a reason for this, which is: the knowledge about the bug stays
> within Qt's systems. What if we submit a change to fix something,
> referencing the blog post, and then that post disappears? We would've
> lost a lot of important information about what the bug was and why the
> fix made sense. So please take the 2 minutes necessary to copy&paste the
> information in the bug report itself.
>

-- 
Roland Hughes, President
Logikal Solutions
(630)-205-1593

http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net
http://www.johnsmith-book.com
http://www.logikalblog.com
http://www.interestingauthors.com/blog
http://lesedi.us/
http://onedollarcontentstore.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20171010/fd992dc5/attachment.html>