From 003654d659141035ec5d326ce5a8ed304ed11286 Mon Sep 17 00:00:00 2001 From: David Grudl Date: Sun, 11 May 2014 18:56:18 +0200 Subject: [PATCH] opened 2.2 --- composer.json | 7 +------ readme.md | 2 +- 2 files changed, 2 insertions(+), 7 deletions(-) diff --git a/composer.json b/composer.json index c226156..14c7cec 100644 --- a/composer.json +++ b/composer.json @@ -25,10 +25,5 @@ "autoload": { "classmap": ["src/"] }, - "minimum-stability": "dev", - "extra": { - "branch-alias": { - "dev-master": "2.2-dev" - } - } + "minimum-stability": "dev" } diff --git a/readme.md b/readme.md index 5f9a593..cb4bd2e 100644 --- a/readme.md +++ b/readme.md @@ -2,7 +2,7 @@ Nette SafeStream: Atomic Operations =================================== [![Downloads this Month](https://img.shields.io/packagist/dm/nette/safe-stream.svg)](https://packagist.org/packages/nette/safe-stream) -[![Build Status](https://travis-ci.org/nette/safe-stream.svg?branch=master)](https://travis-ci.org/nette/safe-stream) +[![Build Status](https://travis-ci.org/nette/safe-stream.svg?branch=v2.2)](https://travis-ci.org/nette/safe-stream) The Nette\Utils\SafeStram protocol for file manipulation guarantees atomicity and isolation of every file operation. Why is it actually good? Let's start with a simple example, where we repeatedly write the same string to the file and then read it: