Jonathan Tan writes:
>> 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.
> 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.
Would it be possible to ha
Hi Jacob,
> * sb/diff-color-move-more (2018-05-21) 8 commits
> (merged to 'next' on 2018-05-24 at 45f3fb7975)
> + diff: color-moved white space handling options imply color-moved
> + diff.c: add --color-moved-ignore-space-delta option
> + diff.c: decouple white space treatment from move detec
Hi Junio,
Junio C Hamano wrote:
> * tz/cred-netrc-cleanup (2018-06-18) 3 commits
> - git-credential-netrc: fix exit status when tests fail
> - git-credential-netrc: use in-tree Git.pm for tests
> - git-credential-netrc: minor whitespace cleanup in test script
>
> Build and test procedure for
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.
As -rc2 has slipped by a few days,
5 matches
Mail list logo
