Re: What's cooking in git.git (Feb 2016, #04; Fri, 12)

Torsten Bögershausen writes: > On 15/02/16 05:50, Junio C Hamano wrote: >> Torsten Bögershausen writes: >> * tb/conversion (2016-02-10) 6 commits (merged to 'next' on 2016-02-12 at 6faf27b) >>> Could we keep it in next for a while ? >>> >>> I found

Re: What's cooking in git.git (Feb 2016, #04; Fri, 12)

On 15/02/16 05:50, Junio C Hamano wrote: Torsten Bögershausen writes: * tb/conversion (2016-02-10) 6 commits (merged to 'next' on 2016-02-12 at 6faf27b) Could we keep it in next for a while ? I found issues that needs to be fixed before going to master, updates follow

Re: What's cooking in git.git (Feb 2016, #04; Fri, 12)

Torsten Bögershausen writes: >> * tb/conversion (2016-02-10) 6 commits >> (merged to 'next' on 2016-02-12 at 6faf27b) > Could we keep it in next for a while ? > > I found issues that needs to be fixed before going to master, > updates follow soonish. Hmph, I somehow thought

Re: What's cooking in git.git (Feb 2016, #04; Fri, 12)

> * tb/conversion (2016-02-10) 6 commits > (merged to 'next' on 2016-02-12 at 6faf27b) Could we keep it in next for a while ? I found issues that needs to be fixed before going to master, updates follow soonish. Thanks -- To unsubscribe from this list: send the line "unsubscribe git" in the

What's cooking in git.git (Feb 2016, #04; Fri, 12)

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