From 26763fb8296485ae5bfc7e2c1965041abebf1418 Mon Sep 17 00:00:00 2001
From: Jeff Handley <jeff.handley@microsoft.com>
Date: Tue, 30 Apr 2013 03:07:03 -0700
Subject: [PATCH 1/3] Fixes #12 with a new PR, updated to reflect pre-release
 and build metadata.

---
 semver.md | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/semver.md b/semver.md
index 2c36693..2bf60d0 100644
--- a/semver.md
+++ b/semver.md
@@ -1,6 +1,24 @@
 Semantic Versioning 2.0.0-rc.2
 ==============================
 
+Summary
+-------
+
+Given a version number *MAJOR*.*MINOR*.*PATCH*, increment
+
+1. the *MAJOR* version when you make incompatible API changes from,
+1. the *MINOR* version when you add functionality in a backwards-compatible
+   manner, and
+1. the *PATCH* version when you make backwards-compatible bug fixes.
+
+Given a version number *MAJOR*.*MINOR*.*PATCH*\[-*PRE-RELEASE*\]\[+*BUILD METADATA*\] where the optional *PRE-RELEASE* and/or *BUILD METADATA* are used, update
+
+1. the *PRE-RELEASE* label when reaching a new pre-release milestone, and/or
+1. the *BUILD METADATA* with every build.
+
+Introduction
+------------
+
 In the world of software management there exists a dread place called
 "dependency hell." The bigger your system grows and the more packages you
 integrate into your software, the more likely you are to find yourself, one

From 663884f86cd66c80041168a0ce76a5e017157a9e Mon Sep 17 00:00:00 2001
From: jeffhandley <jeff@jeffhandley.com>
Date: Fri, 31 May 2013 17:03:57 -0700
Subject: [PATCH 2/3] Remove the details for pre-release and build metadata
 from the summary

---
 semver.md | 13 +++++--------
 1 file changed, 5 insertions(+), 8 deletions(-)

diff --git a/semver.md b/semver.md
index 2bf60d0..f7a3ca0 100644
--- a/semver.md
+++ b/semver.md
@@ -4,17 +4,14 @@ Semantic Versioning 2.0.0-rc.2
 Summary
 -------
 
-Given a version number *MAJOR*.*MINOR*.*PATCH*, increment
+Given a version number MAJOR.MINOR.PATCH, increment
 
-1. the *MAJOR* version when you make incompatible API changes from,
-1. the *MINOR* version when you add functionality in a backwards-compatible
+1. the MAJOR version when you make incompatible API changes from,
+1. the MINOR version when you add functionality in a backwards-compatible
    manner, and
-1. the *PATCH* version when you make backwards-compatible bug fixes.
+1. the PATCH version when you make backwards-compatible bug fixes.
 
-Given a version number *MAJOR*.*MINOR*.*PATCH*\[-*PRE-RELEASE*\]\[+*BUILD METADATA*\] where the optional *PRE-RELEASE* and/or *BUILD METADATA* are used, update
-
-1. the *PRE-RELEASE* label when reaching a new pre-release milestone, and/or
-1. the *BUILD METADATA* with every build.
+Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
 
 Introduction
 ------------

From a5cbaacd711a699b53403ca5f0e34e8e36843ec3 Mon Sep 17 00:00:00 2001
From: jeffhandley <jeff@jeffhandley.com>
Date: Mon, 3 Jun 2013 12:42:54 -0700
Subject: [PATCH 3/3] Cleaned up punctuation and format of summary

---
 semver.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/semver.md b/semver.md
index f7a3ca0..5ac699a 100644
--- a/semver.md
+++ b/semver.md
@@ -4,12 +4,12 @@ Semantic Versioning 2.0.0-rc.2
 Summary
 -------
 
-Given a version number MAJOR.MINOR.PATCH, increment
+Given a version number MAJOR.MINOR.PATCH, increment the:
 
-1. the MAJOR version when you make incompatible API changes from,
-1. the MINOR version when you add functionality in a backwards-compatible
+1. MAJOR version when you make incompatible API changes,
+1. MINOR version when you add functionality in a backwards-compatible
    manner, and
-1. the PATCH version when you make backwards-compatible bug fixes.
+1. PATCH version when you make backwards-compatible bug fixes.
 
 Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.