Re: What's cooking in git.git (Dec 2017, #05; Wed, 27)

2018-01-03 Thread Kaartic Sivaraam
On Wednesday 03 January 2018 02:56 PM, Daniel Knittl-Frank wrote: On Wed, Dec 27, 2017 at 10:34 PM, Junio C Hamano wrote: * dk/describe-all-output-fix (2017-12-27) 1 commit - describe: prepend "tags/" when describing tags with embedded name An old regression in "git

Re: What's cooking in git.git (Dec 2017, #05; Wed, 27)

2018-01-03 Thread Daniel Knittl-Frank
On Wed, Dec 27, 2017 at 10:34 PM, Junio C Hamano wrote: > * dk/describe-all-output-fix (2017-12-27) 1 commit > - describe: prepend "tags/" when describing tags with embedded name > > An old regression in "git describe --all $annotated_tag^0" has been > fixed. > > Will merge

Re: What's cooking in git.git (Dec 2017, #05; Wed, 27)

2018-01-02 Thread Jonathan Nieder
Stefan Beller wrote: > On Thu, Dec 28, 2017 at 11:02 AM, Junio C Hamano wrote: >> Elijah Newren writes: >>> surprised by the branch name, though. Was 'ew/' a typo, >> >> Blush X-<. Yes it is a typo. > > Note on that series: > I have reviewed the first

Re: What's cooking in git.git (Dec 2017, #05; Wed, 27)

2018-01-02 Thread Stefan Beller
On Thu, Dec 28, 2017 at 11:02 AM, Junio C Hamano wrote: > Elijah Newren writes: > >> surprised by the branch name, though. Was 'ew/' a typo, > > Blush X-<. Yes it is a typo. Note on that series: I have reviewed the first three patches (which could form an

Re: What's cooking in git.git (Dec 2017, #05; Wed, 27)

2017-12-28 Thread Junio C Hamano
Elijah Newren writes: > surprised by the branch name, though. Was 'ew/' a typo, Blush X-<. Yes it is a typo.

Re: What's cooking in git.git (Dec 2017, #05; Wed, 27)

2017-12-27 Thread Elijah Newren
On Wed, Dec 27, 2017 at 1:34 PM, Junio C Hamano wrote: > * ew/empty-merge-with-dirty-index (2017-12-22) 1 commit > - Merge branch 'ew/empty-merge-with-dirty-index-maint' into > ew/empty-merge-with-dirty-index > (this branch uses ew/empty-merge-with-dirty-index-maint.) > *

What's cooking in git.git (Dec 2017, #05; Wed, 27)

2017-12-27 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. You can find the changes