Thread (7 messages) flat view 7 messages, 3 authors, 2016-08-08

Re: [PATCH] pack-objects: Use reachability bitmap index when generating non-stdout pack too

From: Kirill Smelkov <hidden>
Date: 2016-07-29 07:41:05

Possibly related (same subject, not in this thread)

On Thu, Jul 28, 2016 at 02:18:29PM -0700, Junio C Hamano wrote:
Kirill Smelkov [off-list ref] writes:
quoted
I'm waiting so long for main patch to be at least queued to pu, that I'm
now a bit frustrated and ready to do something not related to main goal :)
Perhaps the first step would be to stop putting multiple patches in
a single e-mail buried after a few pages of discussion.  I will not
even find that there _are_ multiple patches in the message if I am
not involved directly in the discussion, and the discussion is still
ongoing, because it is likely that I'd skim just a few paragraphs at
the top before going on to other messages.

I won't touch the message I am responding to, as your -- 8< -- cut
mark does not even seem to be a reliable marker between patches
(i.e.  I see something like this that is clearly not a message
boundary:

than `git pack-objects file.pack`. Extracting erp5.git pack from
lab.nexedi.com backup repository:

---- 8< ----
$ time echo 0186ac99 | git pack-objects --stdout --revs >erp5pack-stdout.pack

real    0m22.309s
...
)
Ok, makes sense and my fault. I'm resending each patch as separate
message in reply to this mail.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help