Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-07-09 Thread Junio C Hamano
Jonathan Tan writes: >> * jt/fetch-pack-negotiator (2018-06-15) 7 commits >> - fetch-pack: introduce negotiator API >> - fetch-pack: move common check and marking together >> - fetch-pack: make negotiation-related vars local >> - fetch-pack: use ref adv. to prune "have" sent >> -

Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-07-09 Thread Jonathan Tan
> * jt/fetch-pack-negotiator (2018-06-15) 7 commits > - fetch-pack: introduce negotiator API > - fetch-pack: move common check and marking together > - fetch-pack: make negotiation-related vars local > - fetch-pack: use ref adv. to prune "have" sent > - fetch-pack: directly end negotiation if

Re: ag/rebase-i-rewrite-todo, was Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-07-06 Thread Johannes Schindelin
Hi Junio, On Fri, 6 Jul 2018, Junio C Hamano wrote: > Johannes Schindelin writes: > > > Of course, at that point I will have to look through those 7 patches > > again, if only to verify that yes, they are still the same. > > That is something the patch author must help the reviewer with, no?

Re: ag/rebase-i-rewrite-todo, was Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-07-06 Thread Junio C Hamano
Johannes Schindelin writes: > Of course, at that point I will have to look through those 7 patches > again, if only to verify that yes, they are still the same. That is something the patch author must help the reviewer with, no? Have uncontroversial stuff early in the series, concentrate on

Re: ag/rebase-i-rewrite-todo, was Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-07-06 Thread Johannes Schindelin
Hi Junio, On Fri, 6 Jul 2018, Junio C Hamano wrote: > Johannes Schindelin writes: > > > I would *strongly* encourage you to allow Alban to go back to the small, > > incremental patch series he sent before, because it will make it > > *substantially* easier to not only review, but also develop,

Re: ag/rebase-i-rewrite-todo, was Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-07-06 Thread Junio C Hamano
Johannes Schindelin writes: > The latest iteration of this is here: > https://public-inbox.org/git/20180702105717.26386-5-alban.gr...@gmail.com/T/#r8eea71077745d6f2c839acb6200bb8b2bea579d3 Good. I think we have it in tree now. > I would *strongly* encourage you to allow Alban to go back to

Re: as/safecrlf-quiet-fix, was Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-07-06 Thread Junio C Hamano
Johannes Schindelin writes: > On Tue, 3 Jul 2018, Junio C Hamano wrote: > >> Johannes Schindelin writes: >> >> > On Thu, 28 Jun 2018, Junio C Hamano wrote: >> > >> >> * as/safecrlf-quiet-fix (2018-06-11) 1 commit >> >> (merged to 'next' on 2018-06-13 at b163674843) >> >> + config.c: fix

Re: js/branch-diff, was Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-07-04 Thread Johannes Schindelin
Hi Junio, On Tue, 3 Jul 2018, Junio C Hamano wrote: > Johannes Schindelin writes: > > > Seriously again, I sent a new iteration: > > > > https://public-inbox.org/git/pull.1.v3.git.gitgitgad...@gmail.com/ > > Thanks, will take a look but it is likely that I'll run out of time > today, so

Re: as/safecrlf-quiet-fix, was Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-07-04 Thread Johannes Schindelin
Hi Junio, On Tue, 3 Jul 2018, Junio C Hamano wrote: > Johannes Schindelin writes: > > > On Thu, 28 Jun 2018, Junio C Hamano wrote: > > > >> * as/safecrlf-quiet-fix (2018-06-11) 1 commit > >> (merged to 'next' on 2018-06-13 at b163674843) > >> + config.c: fix regression for core.safecrlf

Re: js/branch-diff, was Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-07-03 Thread Junio C Hamano
Johannes Schindelin writes: > Seriously again, I sent a new iteration: > > https://public-inbox.org/git/pull.1.v3.git.gitgitgad...@gmail.com/ Thanks, will take a look but it is likely that I'll run out of time today, so please be a bit patient.

Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-07-03 Thread Eric Sunshine
On Tue, Jul 3, 2018 at 2:31 PM Elijah Newren wrote: > On Thu, Jun 28, 2018 at 2:40 PM, Junio C Hamano wrote: > > * ds/multi-pack-index (2018-06-25) 24 commits > > pu fails to build for me (with the standard 'make DEVELOPER=1 ...'), > and it appears to come from this series: > > midx.c:567:15:

Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-07-03 Thread Elijah Newren
Hi Derrick, On Thu, Jun 28, 2018 at 2:40 PM, Junio C Hamano wrote: > * ds/multi-pack-index (2018-06-25) 24 commits > - midx: clear midx on repack > - packfile: skip loading index if in multi-pack-index > - midx: prevent duplicate packfile loads > - midx: use midx in approximate_object_count

Re: as/safecrlf-quiet-fix, was Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-07-03 Thread Junio C Hamano
Johannes Schindelin writes: > Hi Junio, > > On Thu, 28 Jun 2018, Junio C Hamano wrote: > >> * as/safecrlf-quiet-fix (2018-06-11) 1 commit >> (merged to 'next' on 2018-06-13 at b163674843) >> + config.c: fix regression for core.safecrlf false >> >> Fix for 2.17-era regression around

js/branch-diff, was Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-07-03 Thread Johannes Schindelin
Hi Junio, On Thu, 28 Jun 2018, Junio C Hamano wrote: > * js/branch-diff (2018-05-16) 19 commits > - fixup! Add a function to solve least-cost assignment problems > - completion: support branch-diff > - branch-diff: add a man page > - branch-diff --dual-color: work around bogus white-space

ag/rebase-i-rewrite-todo, was Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-07-03 Thread Johannes Schindelin
Hi Junio, On Thu, 28 Jun 2018, Junio C Hamano wrote: > * ag/rebase-i-rewrite-todo (2018-06-15) 3 commits > - rebase--interactive: rewrite the edit-todo functionality in C > - editor: add a function to launch the sequence editor > - Merge branch 'bc/t3430-fixup' into ag/rebase-i-rewrite-todo >

as/sequencer-customizable-comment-char, was Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-07-03 Thread Johannes Schindelin
Hi Junio & Aaron, On Thu, 28 Jun 2018, Junio C Hamano wrote: > * as/sequencer-customizable-comment-char (2018-06-28) 1 commit > - sequencer: use configured comment character > > Honor core.commentchar when preparing the list of commits to replay > in "rebase -i". As per

jh/partial-clone, was Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-07-03 Thread Johannes Schindelin
Hi Junio, On Thu, 28 Jun 2018, Junio C Hamano wrote: > * jh/partial-clone (2018-06-12) 1 commit > (merged to 'next' on 2018-06-13 at 818f864b0c) > + list-objects: check if filter is NULL before using > > The recent addition of "partial clone" experimental feature kicked > in when it

as/safecrlf-quiet-fix, was Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-07-03 Thread Johannes Schindelin
Hi Junio, On Thu, 28 Jun 2018, Junio C Hamano wrote: > * as/safecrlf-quiet-fix (2018-06-11) 1 commit > (merged to 'next' on 2018-06-13 at b163674843) > + config.c: fix regression for core.safecrlf false > > Fix for 2.17-era regression around `core.safecrlf`. Is this `maint` material?

Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-06-29 Thread Ævar Arnfjörð Bjarmason
On Thu, Jun 28 2018, Junio C Hamano wrote: > The tip of 'next' has been rewound and it currently has only 4 > topics. Quite a many topics are cooking in 'pu' and need to be > sifted into good bins (for 'next') and the remainder. Help is > appreciated in that area ;-) Per my

Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-06-29 Thread Junio C Hamano
Stefan Beller writes: >> * jt/remove-pack-bitmap-global (2018-06-21) 2 commits >> - pack-bitmap: add free function >> - pack-bitmap: remove bitmap_git global variable >> >> The effort to move globals to per-repository in-core structure >> continues. > > This is mostly done, though Peff seems

Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-06-29 Thread Derrick Stolee
On 6/28/2018 6:42 PM, Stefan Beller wrote: On Thu, Jun 28, 2018 at 2:40 PM Junio C Hamano wrote: * ds/commit-graph-fsck (2018-06-27) 22 commits [...] "git fsck" learns to make sure the optional commit-graph file is in a sane state. Is this ready for 'next'? I hope so, as I plan to

ag/rebase-i-append-todo-help, was Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-06-29 Thread Alban Gruin
Hi Junio, Le 28/06/2018 à 23:40, Junio C Hamano a écrit : > * ag/rebase-i-append-todo-help (2018-06-14) 2 commits > - rebase--interactive: rewrite append_todo_help() in C > - Merge branch 'ag/rebase-p' into ag/rebase-i-append-todo-help > (this branch is used by ag/rebase-i-rewrite-todo.) > >

Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-06-28 Thread Stefan Beller
On Thu, Jun 28, 2018 at 2:40 PM Junio C Hamano wrote: > The tip of 'next' has been rewound and it currently has only 4 > topics. Quite a many topics are cooking in 'pu' and need to be > sifted into good bins (for 'next') and the remainder. Help is > appreciated in that area ;-) Which branches

What's cooking in git.git (Jun 2018, #07; Thu, 28)

2018-06-28 Thread Junio C Hamano
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. The tip of 'next' has been