diff --git a/ChangeLog b/ChangeLog
index 3b1c493..babd3af 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1 +1,174795 @@
-ChangeLog is maintained by "git log".
+commit 8519efc5b37bb19192a6337088707335f9a041af
+Author: Niels de Vos <ndevos@redhat.com>
+Date:   Mon Aug 22 13:37:59 2016 +0200
+
+    doc: release-notes for GlusterFS-3.8.3
+    
+    BUG: 1365934
+    Change-Id: I510a9d4bbf43e364950fe502a154f119861511a3
+    Signed-off-by: Niels de Vos <ndevos@redhat.com>
+
+commit d99f72842595306e9f26a275804bf0f310caba53
+Author: Krutika Dhananjay <kdhananj@redhat.com>
+Date:   Thu Jul 28 21:29:59 2016 +0530
+
+    cluster/afr: Prevent split-brain when bricks are brought off and on in cyclic order
+    
+            Backport of: http://review.gluster.org/15080
+    
+    When the bricks are brought offline and then online in cyclic
+    order while writes are in progress on a file, thanks to inode
+    refresh in write txns, AFR will mostly fail the write attempt
+    when the only good copy is offline. However, there is still a
+    remote possibility that the file will run into split-brain if
+    the brick that has the lone good copy goes offline *after* the
+    inode refresh but *before* the write txn completes (I call it
+    in-flight split-brain in the patch for ease of reference),
+    requiring intervention from admin to resolve the split-brain
+    before the IO can resume normally on the file. To get around this,
+    the patch does the following things:
+    i) retains the dirty xattrs on the file
+    ii) avoids marking the last of the good copies as bad (or accused)
+        in case it is the one to go down during the course of a write.
+    iii) fails that particular write with the appropriate errno.
+    
+    This way, we still have one good copy left despite the split-brain situation
+    which when it is back online, will be chosen as source to do the heal.
+    
+    > Change-Id: I9ca634b026ac830b172bac076437cc3bf1ae7d8a
+    > BUG: 1363721
+    > Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
+    > Reviewed-on: http://review.gluster.org/15080
+    > Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
+    > Smoke: Gluster Build System <jenkins@build.gluster.org>
+    > CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

More commit messages for this ChangeLog can be found at
https://forge.gluster.org/glusterfs-core/glusterfs/commits/v3.8.3
