From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20918 invoked by alias); 10 Jan 2014 04:00:26 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 20847 invoked by uid 89); 10 Jan 2014 04:00:20 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Fri, 10 Jan 2014 04:00:19 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 4728211659E; Thu, 9 Jan 2014 23:00:17 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 44HdpLbat936; Thu, 9 Jan 2014 23:00:17 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id A607B1164CD; Thu, 9 Jan 2014 23:00:15 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 8B4B3E0401; Fri, 10 Jan 2014 08:00:11 +0400 (RET) Date: Fri, 10 Jan 2014 04:00:00 -0000 From: Joel Brobecker To: Samuel Bronson Cc: gdb@sourceware.org Subject: Re: Trailing Whitespace Message-ID: <20140110040011.GA4639@adacore.com> References: <20140109144455.GA2972@blade.nx> <20140109145731.GA13720@localhost.localdomain> <20140109150145.GA3788@adacore.com> <52CEEE7B.50506@samersoff.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2014-01/txt/msg00013.txt.bz2 > > IMHO, better approach is to install on-commit hook blocking commits > > with trailing whitespace (and tab characters) and leave old code as is. > > Unfortunately, commit hooks have to be set up in every local copy of the > repository, which I can't see happening. The best way to do this is to do it on the official repository (on sourceware) - via the "update" hook. We can also provide client-side hooks for the "commit", but, as you say, it would rely on everyone of us activating them. -- Joel