Re: What's cooking in git.git (Sep 2017, #03; Fri, 15)

Hi Junio, On Sat, 16 Sep 2017, Junio C Hamano wrote: > Johannes Schindelin writes: > > > On Fri, 15 Sep 2017, Junio C Hamano wrote: > > > >> -- > >> [Cooking] > >> > >> [...] > >> > >> *

Re: What's cooking in git.git (Sep 2017, #03; Fri, 15)

Sahil Dua writes: > On Fri, Sep 22, 2017 at 5:39 AM, Junio C Hamano wrote: >> >> So here is such an update. As the topic is not in 'next' yet, it >> could also be implemented by replacing patch(es) in the series, but >> doing it as a follow-up fix

Re: What's cooking in git.git (Sep 2017, #03; Fri, 15)

On Fri, Sep 22, 2017 at 5:39 AM, Junio C Hamano wrote: > Junio C Hamano writes: > >> My understanding of the next step was for those who are interested >> in moving this topic forward to update these patches in that >> direction. > > Well, I am one of those

Re: What's cooking in git.git (Sep 2017, #03; Fri, 15)

Junio C Hamano writes: > My understanding of the next step was for those who are interested > in moving this topic forward to update these patches in that > direction. Well, I am one of those who are interested in moving this topic forward, not because I'm likely to use it,

Re: What's cooking in git.git (Sep 2017, #03; Fri, 15)

Sahil Dua writes: >> >> * sd/branch-copy (2017-06-18) 3 commits >> - branch: add a --copy (-c) option to go with --move (-m) >> - branch: add test for -m renaming multiple config sections >> - config: create a function to format section headers >> >> "git branch"

Re: What's cooking in git.git (Sep 2017, #03; Fri, 15)

> > * sd/branch-copy (2017-06-18) 3 commits > - branch: add a --copy (-c) option to go with --move (-m) > - branch: add test for -m renaming multiple config sections > - config: create a function to format section headers > > "git branch" learned "-c/-C" to create and switch to a new branch >

Re: What's cooking in git.git (Sep 2017, #03; Fri, 15)

Lars Schneider writes: > SZEDER noticing a bug in this series that I was about to fix: > https://public-inbox.org/git/3b175d35-5b1c-43cd-a7e9-85693335b...@gmail.com/ > > I assume at this point a new patch is better than a re-roll, right? Thanks, yes indeed.

Re: What's cooking in git.git (Sep 2017, #03; Fri, 15)

Johannes Schindelin writes: > Hi Junio, > > On Fri, 15 Sep 2017, Junio C Hamano wrote: > >> -- >> [Cooking] >> >> [...] >> >> * mk/diff-delta-uint-may-be-shorter-than-ulong (2017-08-10) 1 commit >> ... >> Dropped, as

Re: What's cooking in git.git (Sep 2017, #03; Fri, 15)

Johannes Schindelin writes: > Please stop stating that you expect a reroll for rebase-i-extra when you > explicitly stated months ago that you would not take my v6. It gets a bit > annoying. I already explained to you why I skipped v6, which turned to be identical to

Re: What's cooking in git.git (Sep 2017, #03; Fri, 15)

Hi Junio, On Fri, 15 Sep 2017, Junio C Hamano wrote: > -- > [Cooking] > > [...] > > * mk/diff-delta-uint-may-be-shorter-than-ulong (2017-08-10) 1 commit > . diff-delta: fix encoding size that would not fit in "unsigned int" > > The machinery

Re: What's cooking in git.git (Sep 2017, #03; Fri, 15)

Hi Junio, On Fri, 15 Sep 2017, Junio C Hamano wrote: > * js/rebase-i-final (2017-07-27) 10 commits > - rebase -i: rearrange fixup/squash lines using the rebase--helper > - t3415: test fixup with wrapped oneline > - rebase -i: skip unnecessary picks using the rebase--helper > - rebase -i:

Re: What's cooking in git.git (Sep 2017, #03; Fri, 15)

On 15 Sep 2017, at 07:58, 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