Hi,
On Wed, 5 Jun 2019, Nickolai Belakovski wrote:
> On Thu, May 30, 2019 at 5:20 PM Junio C Hamano wrote:
> >
> > * nb/branch-show-other-worktrees-head (2019-05-07) 3 commits
> > - branch: add worktree info on verbose output
> > - branch: update output to include worktree info
> > - ref-filt
On Thu, May 30, 2019 at 5:20 PM Junio C Hamano wrote:
>
> * nb/branch-show-other-worktrees-head (2019-05-07) 3 commits
> - branch: add worktree info on verbose output
> - branch: update output to include worktree info
> - ref-filter: add worktreepath atom
>
> "git branch --list" learned to sho
On 31/05/2019 18:34, Junio C Hamano wrote:
* po/git-help-on-git-itself (2019-05-16) 2 commits
- Doc: git.txt: remove backticks from link and add git-scm.com/docs
- git.c: show usage for accessing the git(1) help page
"git help git" was hard to discover (well, at least for some
people).
Johannes Schindelin 于2019年6月1日周六 上午4:26写道：
>
> Hi Junio,
>
> On Fri, 31 May 2019, Junio C Hamano wrote:
>
> > Johannes Schindelin writes:
> >
> > >> * cc/list-objects-filter-wo-sparse-path (2019-05-29) 1 commit
> > >> (merged to 'next' on 2019-05-30 at 5a294203ad)
> > >> + list-objects-filter:
Hi Junio,
On 31 May 2019 23:04:38 GMT+05:30, Junio C Hamano wrote:
>Johannes Schindelin writes:
>
>> On Thu, 30 May 2019, Junio C Hamano wrote:
>>> * ds/close-object-store (2019-05-28) 3 commits
>>> - packfile: rename close_all_packs to close_object_store
>>> - packfile: close commit-graph i
Hi Junio,
On Fri, 31 May 2019, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> >> * cc/list-objects-filter-wo-sparse-path (2019-05-29) 1 commit
> >> (merged to 'next' on 2019-05-30 at 5a294203ad)
> >> + list-objects-filter: disable 'sparse:path' filters
> >>
> >> Disable "--filter=sp
Johannes Schindelin writes:
>> * cc/list-objects-filter-wo-sparse-path (2019-05-29) 1 commit
>> (merged to 'next' on 2019-05-30 at 5a294203ad)
>> + list-objects-filter: disable 'sparse:path' filters
>>
>> Disable "--filter=sparse:path=" that would allow reading from
>> paths on the filesyste
Hi Junio,
On Fri, 31 May 2019, Junio C Hamano wrote:
> [...] as I said in "What's cooking" report one issue ago, the criteria
> is no longer "this is obviously correct"---it is "this is obvious and
> trivial fix for a regression".
I heard that, just wanted to give you my stance ;-)
In Git for W
Johannes Schindelin writes:
> On Thu, 30 May 2019, Junio C Hamano wrote:
>
>> * bb/unicode-12.1-reiwa (2019-05-29) 1 commit
>> (merged to 'next' on 2019-05-30 at 016465335c)
>> + unicode: update the width tables to Unicode 12.1
>> <<
>> * bb/unicode-12.1-reiwa (2019-05-29) 1 commit
>> - unico
Hi Junio,
On Fri, 31 May 2019, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> >> The second round of release candidate has been tagged, after slipping
> >> for several days to merge a handful of last-minute regression fixes.
> >
> > You hinted in an earlier "What's cooking" that you'd m
Johannes Schindelin writes:
>> The second round of release candidate has been tagged, after
>> slipping for several days to merge a handful of last-minute
>> regression fixes.
>
> You hinted in an earlier "What's cooking" that you'd maybe go for an -rc3.
> Is that still the case?
That was back w
Hi Junio,
On Thu, 30 May 2019, Junio C Hamano wrote:
> * bb/unicode-12.1-reiwa (2019-05-29) 1 commit
> (merged to 'next' on 2019-05-30 at 016465335c)
> + unicode: update the width tables to Unicode 12.1
> <<
> * bb/unicode-12.1-reiwa (2019-05-29) 1 commit
> - unicode: update the width tables
Hi Junio,
On Thu, 30 May 2019, 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 branches, but I
13 matches
Mail list logo
