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

Re: [PATCH] list-objects-filter-options: fix up some sparse warnings

From
Ramsay Jones <ramsay@ramsayjones.plus.com>
Date
Nov 21, 2017, 11:04 UTC
Message-ID
<b5a6ddb1-0971-92d1-4cfb-94366d8f14c3@ramsayjones.plus.com>
In-Reply-To
<20171121011634.dw6tdgp2s7lpl2lm@aiede.mtv.corp.google.com>
On 21/11/17 01:16, Jonathan Nieder wrote:
Show 10 quoted lines
> Hi,
> 
> Ramsay Jones wrote:
> 
>> If you need to re-roll your 'jh/object-filtering' branch, could you
>> please squash this (or something like it) into the relevant patch
>> (commit bf0aedcbe1, "list-objects: filter objects in traverse_commit_list",
>> 16-11-2017).
> 
> Micronit: can these messages use the ISO 8601 order 2017-11-16?

Hmm, I suppose I could try and train my fingers to use this unnatural order ... ;-)

[It would probably be easier if I used git to output this for me, rather than typing it into my email client!]

ATB, Ramsay Jones

Previous: Jonathan NiederNext: Stefan Beller
Message 3 of 5 in “list-objects-filter-options: fix up some sparse warnings”
  1. list-objects-filter-options: fix up some sparse warningsRamsay Jones, Nov 20, 2017
  2. Jonathan NiederNov 21, 2017
  3. Ramsay JonesNov 21, 2017
  4. Stefan BellerNov 22, 2017
  5. Jeff HostetlerNov 21, 2017

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.