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

Re: [PATCH 0/8] git-repack --max-pack-size

From
DHDana How <danahow@gmail.com>
Date
Apr 9, 2007, 19:43 UTC
Message-ID
<56b7f5510704091243w2ef54809m339663b3fbf72ad6@mail.gmail.com>
In-Reply-To
<46197814.5010909@gmail.com>
On 4/8/07, Dana How <danahow@gmail.com> wrote:
Show 10 quoted lines
> The three most common ways of making large packfiles
> are git-fast-import, the first git-repack, or git-repack -a.
> The first already supports a "--max-pack-size=N" option,
> which limits the resulting packfiles to N megabytes.
> This patchset adds the same option, with the same
> behavior, to git-repack to handle the other two cases.
>
> After reviewing others' comments,  this latest patchset
> touches 2/3 fewer files and 1/6 fewer lines,  and
> introduces no behavior not seen elsewhere in git.
At the moment,  I plan the following changes to this patchset:
* Redo after 64b index applied (Nicolas)
* Bad re-use of header around sha1write (Nicolas)
* Set object_entry.offset before write_object (Dana)
* Finish reducing struct object_entry (Junio)
* Remove spaces from inside () (Junio)

Concerning refactorings, I'd prefer to keep those in a separate (follow-on?) patchset.

Thanks,
-- 
Dana L. How  danahow@gmail.com  +1 650 804 5991 cell
Previous: Dana How
Message 4 of 4 in “git-repack --max-pack-size”
  1. 0/8 git-repack --max-pack-sizeDana How, Apr 8, 2007
  2. Nicolas PitreApr 9, 2007
  3. Dana HowApr 9, 2007
  4. Dana HowApr 9, 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.