Re: What's cooking in git.git (Feb 2017, #02; Mon, 6)

Junio C Hamano writes: > Jeff King writes: > >> On Mon, Feb 06, 2017 at 02:34:08PM -0800, Junio C Hamano wrote: >> >>> * sk/parse-remote-cleanup (2017-02-06) 1 commit >>> (merged to 'next' on 2017-02-06 at 6ec89f72d5) >>> + parse-remote: remove reference to

Re: What's cooking in git.git (Feb 2017, #02; Mon, 6)

Hi Junio, On Thu, 9 Feb 2017, Junio C Hamano wrote: > Johannes Schindelin writes: > > > ... and even go so far as calling your patch reverting my refactoring > > a hot-fix, why don't you just go ahead and merge the result over my > > objections? > > At this point,

Re: What's cooking in git.git (Feb 2017, #02; Mon, 6)

Johannes Schindelin writes: >> > (And that would have to be handled at a different point, as I had >> > pointed out, so that suggested preparation would most likely not help >> > at all.) >> >> I did not think "that would have to be handled at a different point" >>

Re: What's cooking in git.git (Feb 2017, #02; Mon, 6)

Hi Junio, On Thu, 9 Feb 2017, Junio C Hamano wrote: > Johannes Schindelin writes: > > > (And that would have to be handled at a different point, as I had > > pointed out, so that suggested preparation would most likely not help > > at all.) > > I did not think

Re: What's cooking in git.git (Feb 2017, #02; Mon, 6)

Michael Haggerty writes: > On 02/06/2017 11:34 PM, Junio C Hamano wrote: >> [...] >> -- >> [Stalled] >> [...] >> * mh/ref-remove-empty-directory (2017-01-07) 23 commits >> - files_transaction_commit(): clean up empty

Re: What's cooking in git.git (Feb 2017, #02; Mon, 6)

Michael Haggerty writes: > On 02/06/2017 11:34 PM, Junio C Hamano wrote: >> [...] >> -- >> [Stalled] >> [...] >> * mh/ref-remove-empty-directory (2017-01-07) 23 commits >> >> Deletion of a branch "foo/bar" could remove

Re: What's cooking in git.git (Feb 2017, #02; Mon, 6)

Johannes Schindelin writes: > (And that would have to be handled at a different point, as I > had pointed out, so that suggested preparation would most likely not help > at all.) I did not think "that would have to be handled at a different point" is correct at all,

Re: What's cooking in git.git (Feb 2017, #02; Mon, 6)

On 02/06/2017 11:34 PM, Junio C Hamano wrote: > [...] > -- > [Stalled] > [...] > * mh/ref-remove-empty-directory (2017-01-07) 23 commits > - files_transaction_commit(): clean up empty directories > - try_remove_empty_parents(): teach to remove

Re: What's cooking in git.git (Feb 2017, #02; Mon, 6)

Hi Junio, On Mon, 6 Feb 2017, Junio C Hamano wrote: > * sf/putty-w-args (2017-02-01) 5 commits > - SQUASH??? > - connect: Add the envvar GIT_SSH_VARIANT and ssh.variant config > - git_connect(): factor out SSH variant handling > - connect: rename tortoiseplink and putty variables > -

Re: What's cooking in git.git (Feb 2017, #02; Mon, 6)

Jeff King writes: > On Mon, Feb 06, 2017 at 02:34:08PM -0800, Junio C Hamano wrote: > >> * sk/parse-remote-cleanup (2017-02-06) 1 commit >> (merged to 'next' on 2017-02-06 at 6ec89f72d5) >> + parse-remote: remove reference to unused op_prep >> >> Code clean-up. >> >> Will

Re: What's cooking in git.git (Feb 2017, #02; Mon, 6)

On Mon, Feb 06, 2017 at 02:34:08PM -0800, Junio C Hamano wrote: > * sk/parse-remote-cleanup (2017-02-06) 1 commit > (merged to 'next' on 2017-02-06 at 6ec89f72d5) > + parse-remote: remove reference to unused op_prep > > Code clean-up. > > Will merge to 'master'. Hrm. Are the functions in

Re: What's cooking in git.git (Feb 2017, #02; Mon, 6)

Stefan Beller writes: >> * sb/submodule-doc (2017-01-12) 3 commits >> - submodules: add a background story >> - submodule update documentation: don't repeat ourselves >> - submodule documentation: add options to the subcommand > > The first two commits are good to go IIRC

Re: What's cooking in git.git (Feb 2017, #02; Mon, 6)

> * sb/submodule-doc (2017-01-12) 3 commits > - submodules: add a background story > - submodule update documentation: don't repeat ourselves > - submodule documentation: add options to the subcommand > > Needs review. > The first two commits are good to go IIRC as you seemed to be positive

Re: What's cooking in git.git (Feb 2017, #02; Mon, 6)

SZEDER Gábor writes: > All failing tests fail with the same error: > > fatal: unrecognized %(refname:strip=2) argument: strip=2 > > That's because of this topic: > >> * kn/ref-filter-branch-list (2017-01-31) 20 commits Ahh, of course. Let's make sure the series won't

Re: What's cooking in git.git (Feb 2017, #02; Mon, 6)

On Mon, Feb 6, 2017 at 4:24 PM, SZEDER Gábor wrote: >> * sg/completion-refs-speedup (2017-02-06) 13 commits >> - squash! completion: fill COMPREPLY directly when completing refs >> - completion: fill COMPREPLY directly when completing refs >> - completion: list only

Re: What's cooking in git.git (Feb 2017, #02; Mon, 6)

> * sg/completion-refs-speedup (2017-02-06) 13 commits > - squash! completion: fill COMPREPLY directly when completing refs > - completion: fill COMPREPLY directly when completing refs > - completion: list only matching symbolic and pseudorefs when completing refs > - completion: let

What's cooking in git.git (Feb 2017, #02; Mon, 6)

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