git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v3 0/2] EditorConfig file

From
Taylor Blau <me@ttaylorr.com>
Date
Oct 8, 2018, 22:21 UTC
Message-ID
<20181008222118.GA26078@syl>
In-Reply-To
<20181008220353.780301-1-sandals@crustytoothpaste.net>
On Mon, Oct 08, 2018 at 10:03:51PM +0000, brian m. carlson wrote:
Show 12 quoted lines
> This series introduces an EditorConfig file to help developers using any
> editor set their editor's settings in conformance with the Git Project's
> settings.  This is helpful for developers who work on different projects
> with different indentation standards to keep their work in sync.
>
> Changes since v2:
> * Add .pl and .pm files.
>
> Changes since v1:
> * Add notes to both .editorconfig and .clang-format that they should be
>   kept in sync.
> * Add commit message line length.

Thanks for both of these. I think that v3 is ready for queueing, if other folks find it OK to have an .editorconfig in the repository.

Therefore:
  Reviewed-by: Taylor Blau <me@ttaylorr.com>

Thanks, Taylor

Previous: brian m. carlson
Message 4 of 4 in “EditorConfig file”
  1. 0/2 EditorConfig filebrian m. carlson, Oct 8, 2018
  2. 1/2 editorconfig: provide editor settings for Git developersbrian m. carlson, Oct 8, 2018
  3. 2/2 editorconfig: indicate settings should be kept in syncbrian m. carlson, Oct 8, 2018
  4. Taylor BlauOct 8, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.