Re: What's cooking in git.git (May 2015, #06; Fri, 22)

From: Luke Diamand <luke@diamand.org>
Date: May 23, 2015, 19:24 UTC
Message-ID: <5560D3E8.1010704@diamand.org>
In-Reply-To: <xmqqiobkdzv9.fsf@gitster.dls.corp.google.com>

On 22/05/15 23:14, 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'.
>

ry_matches(): inline function

>   + is_> The fourth batch of topics have been merged to 'master'.
>

<snip>

Show 15 quoted lines

>
>
> * ld/p4-editor-multi-words (2015-05-20) 6 commits
>   - SQUASH
>   - git-p4: tests: use test-chmtime in place of touch
>   - SQUASH
>   - git-p4: fix handling of multi-word P4EDITOR
>   - SQUASH
>   - git-p4: add failing test for P4EDITOR handling
>
>   Unlike "$EDITOR" and "$GIT_EDITOR" that can hold the path to the
>   command and initial options (e.g. "/path/to/emacs -nw"), 'git p4'
>   did not let the shell interpolate the contents of the environment
>   variable that name the editor "$P4EDITOR" (and "$EDITOR", too).
>   Make it in line with the rest of Git, as well as with Perforce.

The latest versions in the branch (with the SQUASH) all look good to me.

The other thing still missing from this series is fixing Windows builds. I've been attempting to get a Windows build environment going to actually test it (if it hasn't been tested, it doesn't work.... :-).

I'm slowly getting there, but I'm not very familiar with this particular OS.

Thanks, Luke