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

Re: Rebase max-pack-size?

From
Junio C Hamano <junkio@cox.net>
Date
May 12, 2007, 22:57 UTC
Message-ID
<7vmz09veec.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<56b7f5510705121325h65c62147h2b633fdddaece0be@mail.gmail.com>
"Dana How" <danahow@gmail.com> writes:
> Since max-pack-size has appeared, and disappeard, in "pu" twice
> and never made it into "next",  I'm guessing I should rebase/merge it on
> top of the other recent pack-objects work.  I may get to this tonight;
> perhaps I'll send the patchset in one email with multiple attachments?

I am still holding onto the series on its own topic branch, but merging it to 'pu' and resolving conflicts seem pointless while I am (and hopefully the rest of the list ought to be ;-) primarily concentrating on last-minute bugfixes in preparation for v1.5.2.

A rebase to be queued in 'next' would be good, though.
Thanks.
Message 1 of 1 in “Re: Rebase max-pack-size?”
  1. Junio C HamanoMay 12, 2007

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.