From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-5.9 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by dcvr.yhbt.net (Postfix) with ESMTP id A4B3B1F935 for ; Wed, 21 Sep 2016 17:45:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758551AbcIURpw (ORCPT ); Wed, 21 Sep 2016 13:45:52 -0400 Received: from ikke.info ([178.21.113.177]:40058 "EHLO vps892.directvps.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756421AbcIURpw (ORCPT ); Wed, 21 Sep 2016 13:45:52 -0400 Received: by vps892.directvps.nl (Postfix, from userid 1008) id 2E2B14400A5; Wed, 21 Sep 2016 19:45:50 +0200 (CEST) Date: Wed, 21 Sep 2016 19:45:50 +0200 From: Kevin Daudt To: Junio C Hamano Cc: git@vger.kernel.org Subject: Re: What's cooking in git.git (Sep 2016, #05; Mon, 19) Message-ID: <20160921174550.GB27363@ikke.info> References: <20160921162628.GA27363@ikke.info> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.0 (2016-08-17) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On Wed, Sep 21, 2016 at 10:36:57AM -0700, Junio C Hamano wrote: > Kevin Daudt writes: > > > On Mon, Sep 19, 2016 at 04:30:34PM -0700, Junio C Hamano wrote: > >> > >> * kd/mailinfo-quoted-string (2016-09-19) 2 commits > >> - mailinfo: unescape quoted-pair in header fields > >> - t5100-mailinfo: replace common path prefix with variable > > > > Is this good enough, or do you want me to look into the feedback from > > jeff? > > If you are talking about the simplified loop that deliberately sets > a rule that is looser than RFC, yes, I'd like to see you at least > consider the pros and cons of his approach, which looked nicer to my > brief reading of it. > > It is perfectly OK by me (it may not be so if you ask Peff) if you > decide that your version is better after doing so, though. > > Thanks. Alright, I'll look into it.