From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Stefan Beller <sbeller@google.com>,
git@vger.kernel.org, jonathantanmy@google.com
Subject: Re: [PATCH] RFC: Introduce '.gitorderfile'
Date: Thu, 13 Jul 2017 12:00:14 -0400 [thread overview]
Message-ID: <20170713160014.laowcywx7pb5we77@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqqa849yzwh.fsf@gitster.mtv.corp.google.com>
On Wed, Jul 12, 2017 at 04:54:38PM -0700, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> > I could see somebody arguing that format-patch should respect a project
> > preference, since its primary purpose is to communicate your work to the
> > rest of the project.
> >
> > But then you could make a similar argument for other diff options, too.
>
> Yeah, and that opens a whole can of worms.
>
> We let projects to ship clean/smudge or textconv filters and also
> mark paths to which these tools may be of help, but we do not let
> projects to automatically enable them in the cloned repository. The
> projects must _tell_ the user how to run the last step (e.g. "There
> is a tools/setup-my-clone script shipped with the source; running it
> will add necessary configurations to work better with our project").
>
> I do not think usefulness of diff.orderfile is being questioned, but
> I think it is something we should treat just like any other thing
> that affects repository configuration. A .gitorderfile that allows
> the project to behave as if we allowed to auto-enable just one thing
> in the clone, while not allowing others, a source of issues and
> unnecessary headaches later.
Thanks for writing this out. That was exactly what I was trying to imply
with my final statement, but you said it much better. :)
> Besides, diff-order is *not* the only order that matters in the use
> of the system, and we _will_ regret the name ".gitorderfile" later,
> as people would start making noises about forcing ls-files and other
> things to also show the list following that order.
I'd also agree with this.
-Peff
next prev parent reply other threads:[~2017-07-13 16:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 23:38 [PATCH] RFC: Introduce '.gitorderfile' Stefan Beller
2017-07-12 20:44 ` Junio C Hamano
2017-07-12 20:57 ` Jeff King
2017-07-12 21:08 ` Stefan Beller
2017-07-13 15:59 ` Jeff King
2017-07-13 17:30 ` Stefan Beller
2017-07-13 17:32 ` Brandon Williams
2017-07-13 19:12 ` Junio C Hamano
2017-07-13 19:20 ` Stefan Beller
2017-07-13 20:47 ` Junio C Hamano
2017-07-12 23:54 ` Junio C Hamano
2017-07-13 16:00 ` Jeff King [this message]
2017-07-12 20:58 ` Stefan Beller
2017-07-12 21:37 ` Junio C Hamano
2017-07-12 21:55 ` Stefan Beller
2017-07-12 21:03 ` Ævar Arnfjörð Bjarmason
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170713160014.laowcywx7pb5we77@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jonathantanmy@google.com \
--cc=sbeller@google.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).