From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-3.9 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by dcvr.yhbt.net (Postfix) with ESMTP id 7F82D1F453 for ; Thu, 31 Jan 2019 19:48:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727981AbfAaTsV convert rfc822-to-8bit (ORCPT ); Thu, 31 Jan 2019 14:48:21 -0500 Received: from mail-qk1-f193.google.com ([209.85.222.193]:40495 "EHLO mail-qk1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726994AbfAaTsV (ORCPT ); Thu, 31 Jan 2019 14:48:21 -0500 Received: by mail-qk1-f193.google.com with SMTP id y16so2620513qki.7 for ; Thu, 31 Jan 2019 11:48:20 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=wcrFWWSwI4lH90v1Zplu+c0kt1pTMjM4p8VzZaPEz+8=; b=knIgMQAqb4v5+rzgsn4693PWIfrPBHkEUw30hH90YcdSEhX/1vBjyfGIBglmSK4Ufe qiSGPYXhi7uEXHD3wurLv73yp9OXAMWMVPRetqUFafbZOPmxxAMhnmXBD4E2SHFxubuG PSHCQ7KXhD+oGo8Bl/jeSn/BhNzI0pPs5V/Fcc1sSzA//M+3w7fFx+AT11MElpmhX/m6 ZOnMplVQiH4ZykJt987vJ0Wg2r6WtHRN/Oc3RKvrUP4I2ETSM5C/RkxbfpzxG9xHsscT fwuc4dB+09WxvdC37KkEsjOVZXhN4FqgHA8kr3/21rPrV8VeSES1OKyPp4JBnKC97mOE V94w== X-Gm-Message-State: AJcUukcLItk7iWGsA4UfDRC6SrusKwdb+h6WWj2oxuXfmFBnBuZ1pUcq cFn48t1+w5BGBbbjudF8xA3G5mlZ5R5GSjSIUfs= X-Google-Smtp-Source: ALg8bN4dpbzqMi9Fc3/0hXGmKDpZH6QJq7GU7w9k1IilDwcI6glsYXXJem2weaPcbmiGIOdXXzi5P/jxQTXlQJIu5Oo= X-Received: by 2002:a37:66c1:: with SMTP id a184mr32845835qkc.314.1548964100049; Thu, 31 Jan 2019 11:48:20 -0800 (PST) MIME-Version: 1.0 References: <20190129193818.8645-1-jeremyhu@apple.com> <20190129193818.8645-2-jeremyhu@apple.com> <534F20EC-2B29-46C3-BAD9-3CBE7312257F@apple.com> <8B5241CB-2E1E-4521-8FE1-A84C4896AE82@apple.com> In-Reply-To: From: Eric Sunshine Date: Thu, 31 Jan 2019 14:48:08 -0500 Message-ID: Subject: Re: [PATCH (Apple Git) 01/13] .gitignore: Remove *.s as it matches *.S on case insensitive filesystem To: Jeremy Sequoia Cc: Junio C Hamano , Johannes Schindelin , Git List , Jeff King Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On Thu, Jan 31, 2019 at 1:17 PM Jeremy Sequoia wrote: > > On Jan 31, 2019, at 09:57, Junio C Hamano wrote: > > I still do not see what problem you need a "solution" for in the > > first place---I saw a few comments asking it in the thread, but saw > > no answer. ppc/sha1ppc.S is already tracked, so any modification > > you make in the working tree can be added to the index with "git > > add" and "git status" would report when you have modification to > > that file in the working tree, without any such extra entry in > > .gitignore, no? > > This would have implications for anyone doing something similar or > to anyone intending to add new assembly files to the tree (since > they wouldn’t show up in status or get added with add -A), This nugget finally gives readers an idea of the sort of issue this patch wants to "fix", which happens to be related to HFS+ being case-insensitive. As noted upstream, though, files which are already tracked, such as ppc/sha1ppc.S, are not subject to .gitignore, so Dscho's proposed modification to .gitignore: ... *.[aos] !ppc/sha1ppc.S ... doesn't actually help. Moreover, this .gitignore change doesn't at all help the case you describe about new assembly files not being noticed by "git status" or "git add -A" since any new files won't be named "ppc/sha1ppc.S". As Junio said upstream, .gitignore ignoring "*.s" files is the right thing to do for this project and, as adding new .S files is so rare, it seems unlikely that a patch changing .gitignore to accommodate the above use-case for case-insensitive filesystems would make sense to the project as a whole.