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

DORMANTno replies

Revision v1 of 4 in this series.

4 messages, 2 authors, 2016-06-15 · open the first message on its own page

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

From: Dana How <hidden>
Date: 2016-06-15 22:43:03

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.

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

From: Nicolas Pitre <hidden>
Date: 2016-06-15 22:43:03

On Sun, 8 Apr 2007, Dana How wrote:
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.
I'm starting to like it, but...

I have some extensive changes that touch the same area more or less.  
And so far I think it might be easier to rebase your changes on top of 
mine rather than the other way around.

So I'd like if my changes would be merged first and then yours to be 
applied afterwards.  They still have some issues left anyway.

I'm trying to format my changes now and send them tonight.


Nicolas

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

From: Dana How <hidden>
Date: 2016-06-15 22:43:03

On 4/8/07, Nicolas Pitre [off-list ref] wrote:
On Sun, 8 Apr 2007, Dana How wrote:
quoted
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.
I'm starting to like it, but...

I have some extensive changes that touch the same area more or less.
And so far I think it might be easier to rebase your changes on top of
mine rather than the other way around.

So I'd like if my changes would be merged first and then yours to be
applied afterwards.  They still have some issues left anyway.

I'm trying to format my changes now and send them tonight.
Thanks for sending them out.
I guess I'll update mine to apply after yours once
yours show up in the appropriate branch.

Thanks,
-- 
Dana L. How  danahow@gmail.com  +1 650 804 5991 cell

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

From: Dana How <hidden>
Date: 2016-06-15 22:43:03

On 4/8/07, Dana How [off-list ref] wrote:
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help