Re: What's cooking in git.git (Apr 2019, #03; Tue, 16)

On Wed, Apr 17, 2019 at 03:14:28PM +0900, Junio C Hamano wrote: > Taylor Blau writes: > > >> That's this one > >> > >> Date: Tue, 9 Apr 2019 19:13:06 -0700 (1 week, 3 hours, 23 minutes ago) > >> Subject: [PATCH v2 0/7] harden unexpected object types checks > >> > >> which I think is what h

Re: jt/clone-server-option (was What's cooking in git.git (Apr 2019, #03; Tue, 16))

Jonathan Tan writes: >> Jonathan Tan writes: >> >> >> * jt/clone-server-option (2019-04-15) 4 commits >> >> - SQUASH??? >> >> - clone: send server options when using protocol v2 >> >> - SQUASH??? >> >> - transport: die if server options are unsupported >> >> >> >> "git clone" learned a ne

Re: jc/format-patch-error-check, was Re: What's cooking in git.git (Apr 2019, #03; Tue, 16)

Johannes Schindelin writes: > Hi Junio, > > On Tue, 16 Apr 2019, Junio C Hamano wrote: > >> * jc/format-patch-error-check (2019-02-22) 2 commits >> (merged to 'next' on 2019-04-10 at 6ca358b7ef) >> + format-patch: notice failure to open cover letter for writing >> + builtin/log: downcase the

Re: What's cooking in git.git (Apr 2019, #03; Tue, 16)

Hi Junio, On Tue, Apr 16, 2019 at 10:19:45PM +0900, Junio C Hamano wrote: > * dl/rebase-i-keep-base (2019-04-16) 6 commits > - rebase: teach rebase --keep-base > - rebase: fast-forward --fork-point in more cases > - rebase: fast-forward --onto in more cases > - t3432: test rebase fast-forward

Re: What's cooking in git.git (Apr 2019, #03; Tue, 16)

Ævar Arnfjörð Bjarmason writes: >>> LGTM, but AFAICT this patch of yours never got sent to the list, >>> oversight? >> >> I am reasonably sure that >> was sent with you on >> CC: line. > > My bad, missed it. While juggling several dozens of topics in flight, I'm bound to screw up when it comes

Re: jt/clone-server-option (was What's cooking in git.git (Apr 2019, #03; Tue, 16))

> Jonathan Tan writes: > > >> * jt/clone-server-option (2019-04-15) 4 commits > >> - SQUASH??? > >> - clone: send server options when using protocol v2 > >> - SQUASH??? > >> - transport: die if server options are unsupported > >> > >> "git clone" learned a new --server-option option when ta

ab/test-lib-pass-trace2-env, was Re: What's cooking in git.git (Apr 2019, #03; Tue, 16)

Hi Junio, On Tue, 16 Apr 2019, Junio C Hamano wrote: > * ab/test-lib-pass-trace2-env (2019-04-01) 1 commit > (merged to 'next' on 2019-04-16 at 4dad6d6d7a) > + test-lib: whitelist GIT_TR2_* in the environment > > Allow tracing of Git executable while running out tests. Did you mean "our" ins

jc/format-patch-error-check, was Re: What's cooking in git.git (Apr 2019, #03; Tue, 16)

Hi Junio, On Tue, 16 Apr 2019, Junio C Hamano wrote: > * jc/format-patch-error-check (2019-02-22) 2 commits > (merged to 'next' on 2019-04-10 at 6ca358b7ef) > + format-patch: notice failure to open cover letter for writing > + builtin/log: downcase the beginning of error messages > (this bra

Re: What's cooking in git.git (Apr 2019, #03; Tue, 16)

On Wed, Apr 17 2019, Phillip Wood wrote: > On 16/04/2019 15:51, Ævar Arnfjörð Bjarmason wrote: >> >> On Tue, Apr 16 2019, Junio C Hamano wrote: >> >>> * pw/rebase-i-internal-rfc (2019-03-21) 12 commits >>> - rebase -i: run without forking rebase--interactive >>> - rebase: use a common action

Re: What's cooking in git.git (Apr 2019, #03; Tue, 16)

On 16/04/2019 15:51, Ævar Arnfjörð Bjarmason wrote: On Tue, Apr 16 2019, Junio C Hamano wrote: * pw/rebase-i-internal-rfc (2019-03-21) 12 commits - rebase -i: run without forking rebase--interactive - rebase: use a common action enum - rebase -i: use struct rebase_options in do_interacti

Re: What's cooking in git.git (Apr 2019, #03; Tue, 16)

On Tue, Apr 16, 2019 at 9:51 PM Ævar Arnfjörð Bjarmason wrote: > > * nd/precious (2019-04-09) 1 commit > > - Introduce "precious" file concept > > > > "git clean" learned to pay attention to the 'precious' attributes > > and keep untracked paths with the attribute instead of removing > > when

Re: What's cooking in git.git (Apr 2019, #03; Tue, 16)

On Tue, Apr 16 2019, Junio C Hamano wrote: > Ævar Arnfjörð Bjarmason writes: > >> On Tue, Apr 16 2019, Junio C Hamano wrote: >> >> >>> * jc/gettext-test-fix (2019-04-15) 1 commit >>> - gettext tests: export the restored GIT_TEST_GETTEXT_POISON >>> >>> The GETTEXT_POISON test option has been q

Re: What's cooking in git.git (Apr 2019, #03; Tue, 16)

Taylor Blau writes: >> That's this one >> >> Date: Tue, 9 Apr 2019 19:13:06 -0700 (1 week, 3 hours, 23 minutes ago) >> Subject: [PATCH v2 0/7] harden unexpected object types checks >> >> which I think is what has been queued and what is listed in the >> message you are responding to. > >

Re: What's cooking in git.git (Apr 2019, #03; Tue, 16)

On Wed, Apr 17, 2019 at 02:38:34PM +0900, Junio C Hamano wrote: > Taylor Blau writes: > > > Hi Junio, > > > > On Tue, Apr 16, 2019 at 10:19:45PM +0900, Junio C Hamano wrote: > >> * tb/unexpected (2019-04-10) 7 commits > >> ... > >> Code tightening against a "wrong" object appearing where an objec

Re: What's cooking in git.git (Apr 2019, #03; Tue, 16)

Taylor Blau writes: > Hi Junio, > > On Tue, Apr 16, 2019 at 10:19:45PM +0900, Junio C Hamano wrote: >> * tb/unexpected (2019-04-10) 7 commits >> ... >> Code tightening against a "wrong" object appearing where an object >> of a different type is expected, instead of blindly assuming that >> the

Re: jt/clone-server-option (was What's cooking in git.git (Apr 2019, #03; Tue, 16))

Jonathan Tan writes: >> * jt/clone-server-option (2019-04-15) 4 commits >> - SQUASH??? >> - clone: send server options when using protocol v2 >> - SQUASH??? >> - transport: die if server options are unsupported >> >> "git clone" learned a new --server-option option when talking over >> the

Re: What's cooking in git.git (Apr 2019, #03; Tue, 16)

Ben Peart writes: >> * bp/post-index-change-hook (2019-02-15) 1 commit >>(merged to 'next' on 2019-03-11 at cb96d1d7c4) >> + read-cache: add post-index-change hook >> >> Originally merged to 'next' on 2019-02-23 >> >> A new hook "post-index-change" is called when the on-disk index >>

Re: What's cooking in git.git (Apr 2019, #03; Tue, 16)

Hi Junio, On Tue, Apr 16, 2019 at 10:19:45PM +0900, Junio C Hamano wrote: > * tb/unexpected (2019-04-10) 7 commits > - rev-list: detect broken root trees > - rev-list: let traversal die when --missing is not in use > - get_commit_tree(): return NULL for broken tree > - list-objects.c: handle u

jt/clone-server-option (was What's cooking in git.git (Apr 2019, #03; Tue, 16))

> * jt/clone-server-option (2019-04-15) 4 commits > - SQUASH??? > - clone: send server options when using protocol v2 > - SQUASH??? > - transport: die if server options are unsupported > > "git clone" learned a new --server-option option when talking over > the protocol version 2. > > Getti

Stalled ds/ branches (was What's cooking in git.git (Apr 2019, #03; Tue, 16))

On 4/16/2019 9:19 AM, Junio C Hamano wrote: > * ds/midx-expire-repack (2019-01-27) 10 commits > - midx: add test that 'expire' respects .keep files > - multi-pack-index: test expire while adding packs > - midx: implement midx_repack() > - multi-pack-index: prepare 'repack' subcommand > - mult

Re: What's cooking in git.git (Apr 2019, #03; Tue, 16)

On 4/16/2019 9:19 AM, Junio C Hamano wrote: 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 holdi

Re: What's cooking in git.git (Apr 2019, #03; Tue, 16)

Ævar Arnfjörð Bjarmason writes: > On Tue, Apr 16 2019, Junio C Hamano wrote: > > >> * jc/gettext-test-fix (2019-04-15) 1 commit >> - gettext tests: export the restored GIT_TEST_GETTEXT_POISON >> >> The GETTEXT_POISON test option has been quite broken ever since it >> was made runtime-tunable,

Re: What's cooking in git.git (Apr 2019, #03; Tue, 16)

On Tue, Apr 16 2019, Junio C Hamano wrote: > * jc/gettext-test-fix (2019-04-15) 1 commit > - gettext tests: export the restored GIT_TEST_GETTEXT_POISON > > The GETTEXT_POISON test option has been quite broken ever since it > was made runtime-tunable, which has been fixed. > > Will merge to

What's cooking in git.git (Apr 2019, #03; Tue, 16)

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. Yet another batch of ~30 topics ha