An error occurred while loading the file. Please try again.
-
Thiago Macieira authored
The .gitattributes and .gitignore files do not need to be present in packaged sources, as they are for people using the Git repository. People who download tarballs usually don't reimport into Git -- they should just download the actual repositories. Meanwhile, the .tag file is quite useful. Instead of making Git extract to the useless SHA-1 of the $n string, ask git-archive to store the SHA-1 of the commit being packaged. Change-Id: I8b539dfd4fd1f5bb6891470823184037763267ec Reviewed-by:Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
fc4d3f37
# ==[ Subject: One line only short meaningful description for logs ]===|# ==[ Details: Describe what changed and explain why it changed ]======|# Change log entry (see below for instructions).#[ChangeLog][][]# ==[ Footers: Uncomment and edit where applicable ]===================|## One task per entry. Remember space after colon.#Task-number: ## ==[ Please wrap at 72 characters ]===================================|## Remember to read http://wiki.qt.io/Commit_Policy## Change log entry: If this commit adds a significant feature, fixes an# issue or contains a behavior change that is relevant to others,# add a change log entry. It can be multiple lines long and ends with an# empty newline. Try to integrate it into the flow of the commit message# to avoid redundancy.# Use the module name to indicate the area of the change e.g. [QtCore].# Optionally specify a class or subtopic [QtNetwork][QSslSocket].# Other common tags are: [General], [Important Behavior Changes],# [Platform Specific Changes][Windows][OS X][Linux/XCB].## [ChangeLog][module][class/topic] description of the really important# change that was just made on several lines.