Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:80229 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 49219 invoked from network); 6 Jan 2015 11:33:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Jan 2015 11:33:21 -0000 Authentication-Results: pb1.pair.com smtp.mail=nikita.ppv@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=nikita.ppv@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.178 as permitted sender) X-PHP-List-Original-Sender: nikita.ppv@gmail.com X-Host-Fingerprint: 209.85.212.178 mail-wi0-f178.google.com Received: from [209.85.212.178] ([209.85.212.178:35626] helo=mail-wi0-f178.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 94/13-26786-108CBA45 for ; Tue, 06 Jan 2015 06:33:21 -0500 Received: by mail-wi0-f178.google.com with SMTP id em10so5124908wid.5 for ; Tue, 06 Jan 2015 03:33:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bedbZlynDGCEARJHKj+vl5ZI5bwRVZhtGh6o1v+uxj8=; b=NiFI39LFMcmSc1IqyDnUlWQt9ScEJ/G1szOR6qb77lLGlkvizo8Tft3FnDQWDN09tQ xtJt6mKQHJyCe2Jnv7VKAn+JO96NC8umk2cdnPatTd7eeh/ylvCLm/ULGo3P6eTClBVz uUMp4EQxVYyAXBeUEK/83MQc9Fz6Pv9SzLEXov/pYLQ6fBUiSgvoU8ZrgfuEzKwNm9Mb 1T+sW+XPpK5kw8CEXE4CIFwMZrStJFClIzokbnFdycF9xUTxxtRxIDMfK/eDT1obvYRR CNnHsEhnEKyVZM5aVhdOWkywuE7B4NYQgP455jVSn9TymibEjMoA6M3xqNFRD941G2Ft JvBA== MIME-Version: 1.0 X-Received: by 10.194.79.226 with SMTP id m2mr187087979wjx.60.1420543995971; Tue, 06 Jan 2015 03:33:15 -0800 (PST) Received: by 10.27.10.196 with HTTP; Tue, 6 Jan 2015 03:33:15 -0800 (PST) In-Reply-To: References: <54AB172E.6040901@gmail.com> Date: Tue, 6 Jan 2015 12:33:15 +0100 Message-ID: To: Derick Rethans Cc: Stanislav Malyshev , PHP Internals Content-Type: multipart/alternative; boundary=047d7bf0c538448e65050bfa2c53 Subject: Re: [PHP-DEV] Cleaning up dangling whitespace From: nikita.ppv@gmail.com (Nikita Popov) --047d7bf0c538448e65050bfa2c53 Content-Type: text/plain; charset=UTF-8 On Tue, Jan 6, 2015 at 12:26 PM, Derick Rethans wrote: > On Tue, 6 Jan 2015, Nikita Popov wrote: > > > On Mon, Jan 5, 2015 at 11:58 PM, Stanislav Malyshev > > > wrote: > > > > > The code in the PHP source repo has a lot of random dangling > > > whitespace at the end of lines, which looks sloppy and produces some > > > weird effects in diffs because some editors auto-clean it and some > > > do not. I'd like to clean it up (it's easy to do automatically) in > > > master, but this produces a big patch that may also create some > > > conflicts with existing pull reqs (easily resolved, but still). So, > > > I'd like to ask if there are any objections to such cleanup? If not, > > > then I'll do it, probably next weekend. > > Don't do it for just master, it makes automatic merging possibly a pain. > It should go to all "alive" branches, with properly merged up commits. > > > No objection to whitespace cleanup. iirc git even has options to > > ignore whitespace changes on merge/rebase. > > > > It would be nice to also add a pre-commit hook stripping trailing > > whitespace, to avoid this happening again. > > That would change a commit hash, or cause an extra commit. No thanks. > This is not how pre-commit hooks work. If we only want to check (as opposed to automatically fix), it would be enough to recommend enabling the default pre-commit hook in our git guidelines. Nikita --047d7bf0c538448e65050bfa2c53--