Re: [PATCH v2 00/25] Move exported packfile funcs to its own file

2 messages, 2 authors, 2017-08-10 · open the first message on its own page

Re: [PATCH v2 00/25] Move exported packfile funcs to its own file

From: Junio C Hamano <hidden>
Date: 2017-08-10 21:20:14

Jonathan Tan [off-list ref] writes:
Here is the complete patch set. I have only moved the exported functions
that operate with packfiles and their static helpers - for example,
static functions like freshen_packed_object() that are used only by
non-pack-specific functions are not moved.
This will interfere with smaller changes and fixes we want to have
early in the 'master' branch, so while I think it is a good idea to
do something like this in the longer term, I'd have to ask you to
either hold on or rebase this on them (you'll know what else you are
conflicting with when you try to merge this to 'pu' yourself).

Thanks.

Re: [PATCH v2 00/25] Move exported packfile funcs to its own file

From: Jonathan Tan <hidden>
Date: 2017-08-10 21:59:59

On Thu, 10 Aug 2017 14:19:59 -0700
Junio C Hamano [off-list ref] wrote:
Jonathan Tan [off-list ref] writes:
quoted
Here is the complete patch set. I have only moved the exported functions
that operate with packfiles and their static helpers - for example,
static functions like freshen_packed_object() that are used only by
non-pack-specific functions are not moved.
This will interfere with smaller changes and fixes we want to have
early in the 'master' branch, so while I think it is a good idea to
do something like this in the longer term, I'd have to ask you to
either hold on or rebase this on them (you'll know what else you are
conflicting with when you try to merge this to 'pu' yourself).

Thanks.
OK, I'll wait until you have updated the master branch, then I'll try to
rebase on it.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help