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

Re: [PATCH 5/9] Convert sha1_file.c to size_t

From
Martin Koegler <martin.koegler@chello.at>
Date
Aug 11, 2017, 07:06 UTC
Message-ID
<20170811070600.GB15128@mail.zuhause>
In-Reply-To
<xmqqk22b12jz.fsf@gitster.mtv.corp.google.com>
On Thu, Aug 10, 2017 at 03:27:28PM -0700, Junio C Hamano wrote:
Show 7 quoted lines
> Please do not start your patch series from 5/9 when there is no 1/9,
> 2/9, 3/9, and 4/9.  It is seriously confusing.
> 
> I am guessing that you are trying to split the series into
> manageable pieces by going per call graph and codeflow.  I think it
> is a more sensible approach than a single huge ball of wax we saw
> earlier.

The later patches are further changes extending the previous series. The first, large patch can be splitted any more - it has alreay been generated by changing the delta code and fixing other functions until the codebase is working again.

I didn't wanted to spam the mailing list with the same unchanged patches within a short timeframe.

Regards, Martin

Previous: Junio C Hamano
Message 6 of 6 in “Convert sha1_file.c to size_t”
  1. 5/9 Convert sha1_file.c to size_tMartin Koegler, Aug 10, 2017
  2. 9/9 Convert cache functions to size_tMartin Koegler, Aug 10, 2017
  3. 6/9 Use size_t for sha1Martin Koegler, Aug 10, 2017
  4. 8/9 Convert fsck.c & commit.c to size_tMartin Koegler, Aug 10, 2017
  5. Junio C HamanoAug 10, 2017
  6. Martin KoeglerAug 11, 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.