summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSangmin Seo <sangmin7.seo@samsung.com>2017-08-09 19:07:59 +0900
committerSlava Barinov <v.barinov@samsung.com>2019-12-16 15:28:16 +0300
commitfc1a94cac3b2743c9fbe043b72f4d9de009987d5 (patch)
treec91a1e1fa46d3be1c435333ab24c595ea5191574
parentb01afcb4aa2777698386bdcf68110d1b5e25397f (diff)
downloadbinutils-fc1a94cac3b2743c9fbe043b72f4d9de009987d5.tar.gz
binutils-fc1a94cac3b2743c9fbe043b72f4d9de009987d5.tar.bz2
binutils-fc1a94cac3b2743c9fbe043b72f4d9de009987d5.zip
Add ChangeLog.Tizen
ChangeLog.Tizen is to keep track of private patches for Tizen binutils. Change-Id: I1ca9709cbf7ef92f6d4b29ca7c71782c9541f94a
-rw-r--r--ChangeLog.Tizen60
1 files changed, 60 insertions, 0 deletions
diff --git a/ChangeLog.Tizen b/ChangeLog.Tizen
new file mode 100644
index 00000000000..fdea8df071e
--- /dev/null
+++ b/ChangeLog.Tizen
@@ -0,0 +1,60 @@
+################################################################################
+# Filename: ChangeLog.Tizen
+#
+# Purpose: This file is to keep track of patches that are specific only to
+# Tizen binutils. The goal of this record is to easily determine necessary
+# commits to cherry-pick when we upgrade the major version of Tizen binutils.
+# "Upgrade" here means syncing up with the future release of upstream
+# binutils.
+#
+# What to add here?
+# When we cherry-pick patches from the upstream, we do not need to record
+# them in here because they will be automatically included when upgrading the
+# version. On the other hand, all other patches, which are written only for
+# Tizen, backported from other source, or modified when backporting, should
+# be included in this file.
+#
+# Format:
+# [Commit Date] [Author Name] [Email Address]
+# <empty line>
+# <tab>commit [Commit Hash](optional)
+# <tab>[Commit Message's Subject]
+# <empty line>
+#
+# NOTE-1: Please fit lines in 80 columns.
+# NOTE-2: [Commit Hash] is intended for speeding up the commit search, but it
+# is optional because the permanent commit hash is determined when merging
+# the commit to the main branch, e.g., tizen_base. Therefore, it is not
+# required to include the commit hash if you write your patch and change
+# log at the same time (actually you can't). However, if you update this
+# file after the commit hash is fixed, you are free to add the commit hash.
+################################################################################
+
+2017-08-09 Sangmin Seo <sangmin7.seo@samsung.com>
+
+ Add ChangeLog.Tizen
+
+2017-08-02 Sangmin Seo <sangmin7.seo@samsung.com>
+
+ commit 179bc4ca801cf3fee333246b596e96956084599d
+ ASan build fix: resolve multiple definitions.
+
+2017-06-01 Slava Barinov <v.barinov@samsung.com>
+
+ commit 08a741a1a58641f7d9df899491c0ba08398e7887
+ Introduce --enable-new-dtags configure option.
+
+2017-02-27 Slava Barinov <v.barinov@samsung.com>
+
+ commit 2b741dd730288101ecfe68c5f2270554fd0e48f5
+ 2.27 version
+
+2017-02-27 Yury Usishchev <y.usishchev@samsung.com>
+
+ commit 5a3528e2fcdacd4215291aa6462168d637106475
+ Ignore broken plugins
+
+2017-02-27 Slava Barinov <v.barinov@samsung.com>
+
+ commit fcc5d98409fefd391002a5a8e91b42541234049b
+ Packaging added.