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

Re: [PATCH v2 2/8] sha1-array: Implement oid_array_readonly_contains

From
SZEDER Gábor <szeder.dev@gmail.com>
Date
Jan 29, 2019, 11:15 UTC
Message-ID
<20190129111519.GA14183@szeder.dev>
In-Reply-To
<CABh8og41XhiYzg=X3to7M+zWszJq6a+n8bwHrwkU-GoxYa8-VQ@mail.gmail.com>
On Mon, Jan 28, 2019 at 08:42:23AM -0800, Stefan Xenos wrote:
> Is there a linter script I can run to check for such formatting issues?

Not that I know of, I just happened to notice it while looking into Coccinelle's suggestion about using oideq().

Previous: sxenos@google.com
Message 11 of 11 in “technical doc: add a design doc for the evolve command”
  1. 1/8 technical doc: add a design doc for the evolve commandsxenos@google.com, Jan 27, 2019
  2. 2/8 sha1-array: Implement oid_array_readonly_containssxenos@google.com, Jan 27, 2019
  3. SZEDER GáborJan 28, 2019
  4. 3/8 ref-filter: Add the metas namespace to ref-filtersxenos@google.com, Jan 27, 2019
  5. 4/8 evolve: Add support for parsing metacommitssxenos@google.com, Jan 27, 2019
  6. 5/8 evolve: Add the change-table structuresxenos@google.com, Jan 27, 2019
  7. 6/8 evolve: Add support for writing metacommitssxenos@google.com, Jan 27, 2019
  8. SZEDER GáborJan 29, 2019
  9. 7/8 evolve: Implement the git change commandsxenos@google.com, Jan 27, 2019
  10. 8/8 evolve: Add the git change list commandsxenos@google.com, Jan 27, 2019
  11. SZEDER GáborJan 29, 2019

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.