Remove specific code for upgrade from 2.0 to 2.1
CRM-8813 Message Template fix

----------------------------------------
* CRM-8813: Fix token insert cursor placement issue in Plain Text message body on IE 8
  http://issues.civicrm.org/jira/browse/CRM-8813
Merge pull request #1291 from monishdeb/CRM-8813

CRM-8813 Message Template fix
CRM-13130, fixed notices and using Avery 5395 as default for layout format

----------------------------------------
* CRM-13130: New Label Format entries do not store the 'name' property in values colum, and produce blank name badges
  http://issues.civicrm.org/jira/browse/CRM-13130
Merge pull request #1217 from samuelsov/CRM-10606

CRM-10606 Remove specific code for upgrade from 2.0 to 2.1
CRM-13075 - CRM_Core_BAO_Block - Allow handlePrimary() with entities from extensions

----------------------------------------
* CRM-13075: Mark is_primary for HRJob records
  http://issues.civicrm.org/jira/browse/CRM-13075
Merge pull request #1295 from totten/master-isprimary-tables

CRM-13075 - CRM_Core_BAO_Block - Allow handlePrimary() with entities from extensions
fix patch for CRM-13090

----------------------------------------
* CRM-13090: New Petition/Survey form validation - enforce unique constraint on ActivityType-Campaign-Title
  http://issues.civicrm.org/jira/browse/CRM-13090
Merge pull request #1296 from dlobo/CRM-13090

fix patch for CRM-13090
Merge pull request #1293 from kurund/CRM-13130

CRM-13130, fixed notices and using Avery 5395 as default for layout form...
CRM-13141 restructured code to handle empty 200 result from public extensions directory.

----------------------------------------
* CRM-13141: Manage Extensions throws an erroneous fatal error - Failed Fetching List - when there are no extensions available for a particular install version
  http://issues.civicrm.org/jira/browse/CRM-13141
CRM-13139 - CRM_Utils_REST - Accept empty JSON objects ("{}")

Note: When the "json" parameter includes malformed JSON (eg "{") or an empty
string (""), the behavior is unchanged. This only affects a well-formed empty-obect.

----------------------------------------
* CRM-13139: REST API: json_decode() fails for empty input
  http://issues.civicrm.org/jira/browse/CRM-13139
Merge pull request #1299 from totten/master-rest-empty-json

CRM-13139 - CRM_Utils_REST - Accept empty JSON objects ("{}")
Corrected issue in patch noted by Tim on PR.
Merge pull request #1298 from davecivicrm/CRM-13141

CRM-13141 restructured code to handle empty 200 result from public exten...
test for non-fast forward commits
 second commit to the checking of fast forward commit