From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org, Taylor Blau <me@ttaylorr.com>
Subject: Re: [PATCH] Add an EditorConfig file
Date: Mon, 24 Sep 2018 13:05:23 -0700 [thread overview]
Message-ID: <xmqqefdislto.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20180921225039.GC432229@genre.crustytoothpaste.net> (brian m. carlson's message of "Fri, 21 Sep 2018 22:50:40 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
>> But that is a response in a dream-world. If there is no such tool,
>> I am perfectly OK if the plan is to manually keep them (loosely) in
>> sync. I do not think it is good use of our time to try to come up
>> with such a tool (unless somebody is really interested in doing it,
>> that is).
>
> Would it be helpful if I sent a script that ran during CI to ensure they
> stayed in sync for the couple places where they overlap? I'm happy to
> do so if you think it would be useful.
It may even be an overkill.
A comment addressed to those who edit one file to look at the other
file on both files would be sufficient, I suspect.
next prev parent reply other threads:[~2018-09-24 20:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 23:03 [PATCH] Add an EditorConfig file brian m. carlson
2018-09-17 23:18 ` Taylor Blau
2018-09-20 0:05 ` brian m. carlson
2018-09-19 3:00 ` Junio C Hamano
2018-09-20 0:00 ` brian m. carlson
2018-09-20 14:08 ` Junio C Hamano
2018-09-21 22:50 ` brian m. carlson
2018-09-24 20:05 ` Junio C Hamano [this message]
2018-09-27 22:33 ` brian m. carlson
2018-09-21 2:26 ` Eric Sunshine
2018-09-21 2:35 ` Jeff King
2018-09-21 22:19 ` brian m. carlson
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=xmqqefdislto.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=sandals@crustytoothpaste.net \
/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).