Re: preserve untracked cache, was Re: What's cooking in git.git (Jun 2017, #01; Thu, 1)

Hi Junio, On Sat, 3 Jun 2017, Junio C Hamano wrote: > Johannes Schindelin writes: > > > On Fri, 2 Jun 2017, Junio C Hamano wrote: > > > >> Samuel Lijin writes: > >> > >> >> What is holding this topic up? Anything Ben or I can do to move this >

Re: public inbox links, was: Re: preserve untracked cache, was Re: What's cooking in git.git (Jun 2017, #01; Thu, 1)

Stefan Beller wrote: > Today I learned again how public-inbox is awesome! Thanks Eric! You're welcome :) > * You can just copy the message ID INCLUDING the surrounding < > > and public inbox still just shows you the correct message. I had assumed > you would need to

public inbox links, was: Re: preserve untracked cache, was Re: What's cooking in git.git (Jun 2017, #01; Thu, 1)

On Fri, Jun 2, 2017 at 5:26 PM, Junio C Hamano wrote: > > Issue #06 of May marked it to be merged to 'next': > https://public-inbox.org/git/ > > Issue #07 of May marked it for 'master': >

Re: preserve untracked cache, was Re: What's cooking in git.git (Jun 2017, #01; Thu, 1)

Johannes Schindelin writes: > Hi Junio, > > On Fri, 2 Jun 2017, Junio C Hamano wrote: > >> Samuel Lijin writes: >> >> >> What is holding this topic up? Anything Ben or I can do to move this >> >> closer to `next` or even `master`? >> > >> > It's

Re: preserve untracked cache, was Re: What's cooking in git.git (Jun 2017, #01; Thu, 1)

Hi Junio, On Fri, 2 Jun 2017, Junio C Hamano wrote: > Samuel Lijin writes: > > >> What is holding this topic up? Anything Ben or I can do to move this > >> closer to `next` or even `master`? > > > > It's in `next` right now (3196d093d6). > > Thanks for pinging and checking

Re: preserve untracked cache, was Re: What's cooking in git.git (Jun 2017, #01; Thu, 1)

Samuel Lijin writes: >> What is holding this topic up? Anything Ben or I can do to move this >> closer to `next` or even `master`? > > It's in `next` right now (3196d093d6). Thanks for pinging and checking ;-) I think the topic was merged to 'next' on the 23rd of last

Re: What's cooking in git.git (Jun 2017, #01; Thu, 1)

Johannes Sixt writes: >> Waiting for an Ack to the SQUASH fix or a reroll of the tip commits. > > ACK! > > See also > https://public-inbox.org/git/2899d715-a416-1852-4399-28af0a3e9...@kdbg.org/ > > -- Hannes Thanks.

Re: What's cooking in git.git (Jun 2017, #01; Thu, 1)

Am 01.06.2017 um 09:44 schrieb Junio C Hamano: * nd/fopen-errors (2017-05-30) 14 commits - mingw_fopen: report ENOENT for invalid file names - SQUASH??? use test_i18ngrep and add it at the end - mingw: verify that paths are not mistaken for remote nicknames - log: fix memory leak in

Re: preserve untracked cache, was Re: What's cooking in git.git (Jun 2017, #01; Thu, 1)

On Thu, Jun 1, 2017 at 2:56 PM, Johannes Schindelin wrote: > Hi Junio, > > On Thu, 1 Jun 2017, Junio C Hamano wrote: > >> * dt/unpack-save-untracked-cache-extension (2017-05-20) 1 commit >> (merged to 'next' on 2017-05-23 at 3196d093d6) >> + unpack-trees: preserve

preserve untracked cache, was Re: What's cooking in git.git (Jun 2017, #01; Thu, 1)

Hi Junio, On Thu, 1 Jun 2017, Junio C Hamano wrote: > * dt/unpack-save-untracked-cache-extension (2017-05-20) 1 commit > (merged to 'next' on 2017-05-23 at 3196d093d6) > + unpack-trees: preserve index extensions > > When "git checkout", "git merge", etc. manipulates the in-core > index,

What's cooking in git.git (Jun 2017, #01; Thu, 1)

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. A bit more topics are now in