X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Thu, 7 Jan 2016 05:56:18 +0100 (CET) X-X-Sender: igor2 AT igor2priv To: "Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com]" X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu" From: gedau AT igor2 DOT repo DOT hu Subject: Re: [geda-user] Merging stuff. How to make it happen In-Reply-To: Message-ID: References: <20160106192411 DOT 7d9fd782 AT jive DOT levalinux DOT org> <20160106190750 DOT 32335 DOT qmail AT stuge DOT se> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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 On Thu, 7 Jan 2016, Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com] wrote: >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 Btw, if the project does decide to auto-reformat, please advertise this on the list, there may be forks out there. I have the opposite of your problem: I'd like to reformat pcb-rnd, but so far resisted the temptation to make my patches easier to apply to mainline or other forks. Once the mainline makes that move, I won't have a reason not to do it, this why I'd like to know about it by the time it happens. Regards, Igor2