Merge remote-tracking branch 'upstream/master' into xtensa-v1.0.0

Author: arnabcdns

.gitallowed

@@ -0,0 +1,24 @@
+(?# Floating point numbers)
+[0-9]+\.[0-9]+
+
+(?# Long integer literals)
+[0-9]+L
+
+(?# 2^64-1)
+18446744073709551615
+
+(?# 2^64)
+18446744073709551616
+
+(?# From http parser test)
+0GPHKXSJQ826RK7GZEB2
+
+(?# From uint parse test)
+18446744073709551615
+10000000000000000000
+9223372036854775807G
+
+(?# Found in:)
+(?# esp-idf/components/nghttp/nghttp2/third-party/http-parser/test.c)
+(?# Part of the URL to the page on dan brown)
+0SHYY5BZXN3KR20BNFAY

.gitattributes

@@ -0,0 +1,110 @@
+#common settings that generally should always be used with your language specific settings
+
+# Auto detect text files and perform LF normalization
+# http://davidlaing.com/2012/09/19/customise-your-gitattributes-to-become-a-git-ninja/
+* text=auto
+
+#
+# The above will handle all files NOT found below
+#
+
+# Documents
+*.doc    diff=astextplain
+*.DOC    diff=astextplain
+*.docx diff=astextplain
+*.DOCX diff=astextplain
+*.dot  diff=astextplain
+*.DOT  diff=astextplain
+*.pdf  diff=astextplain
+*.PDF    diff=astextplain
+*.rtf    diff=astextplain
+*.RTF    diff=astextplain
+*.md text
+*.adoc text
+*.textile text
+*.mustache text
+*.csv text
+*.tab text
+*.tsv text
+*.sql text
+
+# Graphics
+*.png binary
+*.jpg binary
+*.jpeg binary
+*.gif binary
+*.tif binary
+*.tiff binary
+*.ico binary
+# SVG treated as an asset (binary) by default. If you want to treat it as text,
+# comment-out the following line and uncomment the line after.
+*.svg binary
+#*.svg text
+*.eps binary
+
+#sources
+*.c text
+*.cc text
+*.cxx text
+*.cpp text
+*.c++ text
+*.hpp text
+*.h text
+*.h++ text
+*.hh text
+
+# Compiled Object files
+*.slo binary
+*.lo binary
+*.o binary
+*.obj binary
+
+# Precompiled Headers
+*.gch binary
+*.pch binary
+
+# Compiled Dynamic libraries
+*.so binary
+*.dylib binary
+*.dll binary
+
+# Compiled Static libraries
+*.lai binary
+*.la binary
+*.a binary
+*.lib binary
+
+# Executables
+*.exe binary
+*.out binary
+*.app binary
+
+
+# Basic .gitattributes for a python repo.
+
+# Source files
+# ============
+*.pxd       text
+*.py        text
+*.py3       text
+*.pyw       text
+*.pyx       text
+
+# Binary files
+# ============
+*.db        binary
+*.p         binary
+*.pkl       binary
+*.pyc       binary
+*.pyd       binary
+*.pyo       binary
+
+# Note: .db, .p, and .pkl files are associated
+# with the python modules ``pickle``, ``dbm.*``,
+# ``shelve``, ``marshal``, ``anydbm``, & ``bsddb``
+# (among others).
+
+*.sh text
+make text
+makefile text
+*.mk text

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,43 @@
+---
+name: Bug report
+about: Create a bug report for Amazon FreeRTOS
+labels: bug
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**System information**
+- Which hardware board or part numbers?
+- IDE used
+- Operating System [Windows|Linux|MacOS]
+- Version of Amazon FreeRTOS (run ``git describe --tags`` to find it)
+- Project [Custom Application|MQTT|Shadow|Greengrass|OTA|Device Defender|TCP Echo|Sub pub Demo|Simple TCP Server]
+- If your project is a Custom Application, please add the relevant code snippet in the section `Code to reproduce the bug`. 
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots or console output**
+If appropriate, please cut-and-paste the console output to explain the issue. If possible, include the call stack. 
+
+**To reproduce**
+Steps to reproduce the behavior:
+
+1. ...
+2. ...
+
+**Code to reproduce the bug**
+The code should be wrapped in the cpp tag in order to be displayed clearly. For example:
+
+```cpp
+printf("Hello World")
+```
+
+If the code is longer than 30 lines, [GIST](https://gist.github.com) is preferred.
+
+**Additional context**
+Add any other context about the problem here.
+
+Thank you!

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,17 @@
+---
+name: Feature request
+about: Suggest an idea for Amazon FreeRTOS
+labels: feature request
+
+---
+
+**Is your feature request related to a problem? Please describe.**  
+A clear and concise description of what the problem is. What are the use cases of the feature to be added? 
+
+**Describe the solution you would like.**  
+A clear and concise description of what you want to happen.
+
+**Additional context**  
+Add any other information (including rationale, requirements, or references) about the feature request here.
+
+Thank you!

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,12 @@
+<!--- Title -->
+
+Description
+-----------
+<!--- Describe your changes in detail -->
+
+Checklist:
+----------
+<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
+<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
+- [ ] I have tested my changes. No regression in existing tests.
+- [ ] My code is Linted.

.gitignore

@@ -0,0 +1,3 @@
+# Ignore uncrustify backups
+*.unc*
+doc/html/*

.gitmessage

@@ -0,0 +1,48 @@
+
+# <Type>: <Subject text> # 50-char limit #########
+# 72-character lines for description ###################################
+
+# Why:
+
+# Related Issues:
+
+# References:
+
+# Run git config commit.template .gitmessage
+# Use git commit when committing files, and this template will be used.
+
+# Example commit message:
+# chore: Add commit message template
+
+# Capitalize subject line.
+# Write capitalized imperative statement with no period for subject
+# List details of significant changes below the subject line
+# Write details as capitalized imperative statements
+# Provide the below sections for further context
+
+# Why:
+
+# A short imperative subject helps when viewing the log, especially when
+# viewing one-line formatted logs.  Clear writing of what changed helps
+# give a clean understanding of context when reading blame messages and
+# when looking at a specific commit.
+
+# Related Issues:
+# Link to related issue numbers (hyper link if applicable), e.g.:
+# git issue 123
+
+# References:
+# List relevant references e.g.:
+# https://chris.beams.io/posts/git-commit/
+
+# Type can be
+#    chore    (updating grunt tasks etc; no production code change)
+#    docs     (changes to documentation, comments.  No logic change)
+#    feat     (New feature)
+#    fix      (Bug fix, or other change related to tracked issue)
+#    merge    (Merge of one branch into another, no other change)
+#    refactor (refactoring production code)
+#    revert   (Revert of a previous commit, no other change)
+#    style    (formatting, missing semi colons, etc; no code change)
+#    test     (adding or refactoring tests; no production code change)
+#    tool     (adding or refactoring tools; no production code change)