From: Christoph Hellwig <hch@infradead.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Leonardo Bras <leobras@redhat.com>,
Randy Dunlap <rdunlap@infradead.org>,
Nicolas Schier <nicolas@fjasle.eu>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [RFC PATCH v5 1/1] scripts: Introduce a default git.orderFile
Date: Tue, 12 Dec 2023 05:08:34 -0800 [thread overview]
Message-ID: <ZXhbUmxzH6nWAzaw@infradead.org> (raw)
In-Reply-To: <CAK7LNAQiJW0eFYQZN0wuURhrdc-8y7=TcEazpxhLf=+mRbKHHQ@mail.gmail.com>
On Tue, Dec 12, 2023 at 05:09:21PM +0900, Masahiro Yamada wrote:
> Unlike .gitignore, this feature is opt-in rather than enforced.
>
> To use this, you need to run
>
> 'git config diff.orderFile scripts/git.orderFile'
>
> or
>
> 'git diff -C scripts/git.orderFile'
Oh, ok. That greatly reduces my concern.
>
> Indeed, the file order is subjective, leaving
> us a question "do we need it in upstream"?
>
> At least, it is harmless for people who have no interest.
.. but this is still a good question. I'm not really sure there is
much of a need for it, but as long as it doesn't harm everyone else
I'm at least neutral on it.
next prev parent reply other threads:[~2023-12-12 13:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 18:18 [RFC PATCH v5 1/1] scripts: Introduce a default git.orderFile Leonardo Bras
2023-12-09 19:13 ` Masahiro Yamada
2023-12-11 13:13 ` lsoaresp
2023-12-11 13:17 ` Leonardo Bras Soares Passos
2023-12-11 18:05 ` Masahiro Yamada
2023-12-11 22:03 ` lsoaresp
2023-12-11 22:41 ` leobras
2023-12-12 7:31 ` Christoph Hellwig
2023-12-12 8:09 ` Masahiro Yamada
2023-12-12 13:08 ` Christoph Hellwig [this message]
2023-12-12 17:09 ` Leonardo Bras
2023-12-15 17:02 ` Masahiro Yamada
2023-12-15 18:30 ` Leonardo Bras Soares Passos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZXhbUmxzH6nWAzaw@infradead.org \
--to=hch@infradead.org \
--cc=leobras@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mchehab@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=rdunlap@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox