From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <lars.winterfeld@tu-ilmenau.de>
Received: from wega.rz.tu-ilmenau.de (wega.rz.tu-ilmenau.de [141.24.4.159])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Thu,  6 Mar 2014 22:05:22 +0100 (CET)
Received: from [192.168.66.2] (erft-5d808bb8.pool.mediaWays.net
 [93.128.139.184]) (authenticated bits=0)
 by wega.rz.tu-ilmenau.de (8.12.11/8.12.11/Debian-3) with ESMTP id
 s26Kd8oi023684
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT)
 for <dm-crypt@saout.de>; Thu, 6 Mar 2014 21:39:09 +0100
Message-ID: <5318DCEF.5020004@tu-ilmenau.de>
Date: Thu, 06 Mar 2014 21:39:11 +0100
From: Lars Winterfeld <lars.winterfeld@tu-ilmenau.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [dm-crypt] goto patch for cryptsetup?
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

Hi,

in light of the latest "goto fail"s out there, would you reject a patch
replacing all 328 gotos with their semantic equivalents from structured
C programming?

Best wishes,
Lars