X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=zEbaM6TxOslMbrubzZqWFD1iW/sxzqGxgB6CRUSlB+g=; b=W05neg8Ens5bTpawe1hQGMdzngZG5K1BOobKRA96B+SE6qU7MvLFgANec2szfcnPjv tBHQKAohyfX3f2BybcUea6CFy8YpSaTjbYuBsBE8wwv+D7D5DSV2UDAdrD919+t9ygEe iJ+jmq/obTM0UGS6ciJrf0rcWRVsKxibEjTx12RU62pNLKAxhGzOU3yH5ux82YtWwqI4 qUbjtJnrbSTnJu9CEz78gp+HsWu/6dSOGIdJfJCE8KZ0gqrDe+dGxbFU4TnjU23q+4tV HV5jeh24nAl90qW3v/idcG4JtALbqp8+1gAOtjU1sq7BBHdRE8qv//EXqc3Wk9GVPFpt f/lw== MIME-Version: 1.0 X-Received: by 10.60.59.101 with SMTP id y5mr43398483oeq.61.1452141454694; Wed, 06 Jan 2016 20:37:34 -0800 (PST) In-Reply-To: <20160106190750.32335.qmail@stuge.se> References: <20160106192411 DOT 7d9fd782 AT jive DOT levalinux DOT org> <20160106190750 DOT 32335 DOT qmail AT stuge DOT se> Date: Thu, 7 Jan 2016 04:37:34 +0000 Message-ID: Subject: Re: [geda-user] Merging stuff. How to make it happen From: "Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com]" To: gEDA User Mailing List Content-Type: multipart/alternative; boundary=089e0149d164921f230528b7072b Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk --089e0149d164921f230528b7072b Content-Type: text/plain; charset=UTF-8 Indeed - we can document requirements, but auto-reformating large chunks of the code will cause un-necessary pain for people (like myself), who have outstanding patches that eventually want to be finished up and committed to HEAD. Peter On 6 January 2016 at 19:07, Peter Stuge (peter AT stuge DOT se) [via geda-user AT delorie DOT com] wrote: > Lev (leventelist AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: > > Should we setup astyle to do the right thing? > > I think it may be very beneficial to us to enforce a coding style in > the future, but I don't think now is the best time. Let's see in a > few months. > > > //Peter > --089e0149d164921f230528b7072b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Indeed - we can document requirements, but auto-refor= mating large chunks of the code will cause un-necessary pain for people (li= ke myself), who have outstanding patches that eventually want to be finishe= d up and committed to HEAD.

Peter
--089e0149d164921f230528b7072b--