Re: What's cooking in git.git (Oct 2017, #07; Mon, 30)

Jonathan Tan writes: > Junio, would you prefer that the combined effort be in one single patch > series or separated out into 3? The way I see it, there are two > independent patch series - this one (object filter support in rev-list > and pack-objects) and my one (repo

Re: What's cooking in git.git (Oct 2017, #07; Mon, 30)

On Wed, 01 Nov 2017 10:21:20 +0900 Junio C Hamano wrote: > Jeff Hostetler writes: > > >> Yes, that, together with the expectation that I will hear from both you > >> and JTan > >> once the result of combined effort becomes ready to replace

Re: What's cooking in git.git (Oct 2017, #07; Mon, 30)

Jeff Hostetler <jeff.hostet...@microsoft.com> writes: > From: Junio C Hamano [mailto:gits...@pobox.com] > Subject: Re: What's cooking in git.git (Oct 2017, #07; Mon, 30) > >> Jeff Hostetler <g...@jeffhostetler.com> writes: >> >>> I've been ass

Re: What's cooking in git.git (Oct 2017, #07; Mon, 30)

Hi Junio, On Tue, 31 Oct 2017, Junio C Hamano wrote: > Johannes Schindelin writes: > > > On Mon, 30 Oct 2017, Junio C Hamano wrote: > > > >> * jc/branch-name-sanity (2017-10-14) 3 commits > >> (merged to 'next' on 2017-10-16 at 174646d1c3) > >> + branch: forbid

RE: What's cooking in git.git (Oct 2017, #07; Mon, 30)

From: Junio C Hamano [mailto:gits...@pobox.com] Subject: Re: What's cooking in git.git (Oct 2017, #07; Mon, 30) > Jeff Hostetler <g...@jeffhostetler.com> writes: > >> I've been assuming that the jt/partial-clone-lazy-fetch is a >> placeholder for our next combin

Re: What's cooking in git.git (Oct 2017, #07; Mon, 30)

Jeff Hostetler writes: > I've been assuming that the jt/partial-clone-lazy-fetch is a > placeholder for our next combined patch series. Yes, that, together with the expectation that I will hear from both you and JTan once the result of combined effort becomes ready to

Re: What's cooking in git.git (Oct 2017, #07; Mon, 30)

Johannes Schindelin writes: > Hi Junio, > > On Mon, 30 Oct 2017, Junio C Hamano wrote: > >> * jc/branch-name-sanity (2017-10-14) 3 commits >> (merged to 'next' on 2017-10-16 at 174646d1c3) >> + branch: forbid refs/heads/HEAD >> + branch: split

Re: What's cooking in git.git (Oct 2017, #07; Mon, 30)

On 10/30/2017 1:31 PM, Johannes Schindelin wrote: Hi Junio, On Mon, 30 Oct 2017, Junio C Hamano wrote: * jt/partial-clone-lazy-fetch (2017-10-02) 18 commits - fetch-pack: restore save_commit_buffer after use - unpack-trees: batch fetching of missing blobs - clone: configure

Re: What's cooking in git.git (Oct 2017, #07; Mon, 30)

Hi Junio, On Mon, 30 Oct 2017, Junio C Hamano wrote: > * jt/partial-clone-lazy-fetch (2017-10-02) 18 commits > - fetch-pack: restore save_commit_buffer after use > - unpack-trees: batch fetching of missing blobs > - clone: configure blobmaxbytes in created repos > - clone: support excluding

Re: What's cooking in git.git (Oct 2017, #07; Mon, 30)

Hi Junio, On Mon, 30 Oct 2017, Junio C Hamano wrote: > * jc/branch-name-sanity (2017-10-14) 3 commits > (merged to 'next' on 2017-10-16 at 174646d1c3) > + branch: forbid refs/heads/HEAD > + branch: split validate_new_branchname() into two > + branch: streamline "attr_only" handling in

Re: What's cooking in git.git (Oct 2017, #07; Mon, 30)

Hi Junio, On Mon, 30 Oct 2017, Junio C Hamano wrote: > * cc/git-packet-pm (2017-10-30) 7 commits > - fixup! Git/Packet.pm: extract parts of t0021/rot13-filter.pl for reuse I am really terribly sorry for the breakage I introduced here. Junio, would you mind amending this commit by deleting the

Re: What's cooking in git.git (Oct 2017, #07; Mon, 30)

* av/fsmonitor (2017-10-30) 5 commits - SQUASH??? - fsmonitor: delay updating state until after split index is merged - fsmonitor: document GIT_TRACE_FSMONITOR - fsmonitor: don't bother pretty-printing JSON from watchman - fsmonitor: set the PWD to the top of the working tree (this

What's cooking in git.git (Oct 2017, #07; Mon, 30)

Here are the topics that have been cooking. Commits prefixed with '-' are only in 'pu' (proposed updates) while commits prefixed with '+' are in 'next'. The ones marked with '.' do not appear in any of the integration branches, but I am still holding onto them. You can find the changes