git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2016, #01; Fri, 1)
Date: Sat, 2 Jul 2016 13:09:42 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1607021306320.12947@virtualbox> (raw)
In-Reply-To: <xmqqmvm0vry4.fsf@gitster.mtv.corp.google.com>

Hi Junio,

On Fri, 1 Jul 2016, Junio C Hamano wrote:

> * jc/t2300-setup (2016-06-22) 1 commit
>   (merged to 'next' on 2016-06-28 at 62b902a)
>  + t2300: "git --exec-path" is not usable in $PATH on Windows as-is
> 
>  Portability fix for Windows.
> 
>  Will merge to 'master'.

Would you mind cherry-picking this onto `maint`, too? I just noticed that
the test suite does not pass here because `maint` has fe17fc0 (t2300: run
git-sh-setup in an environment that better mimics the real life,
2016-06-01).

While at it, it would be nice if this patch:

> * js/mingw-parameter-less-c-functions (2016-06-20) 1 commit
>   (merged to 'next' on 2016-06-28 at e673c65)
>  + mingw: let the build succeed with DEVELOPER=1
> 
>  Some platform-specific code had non-ANSI strict declarations of C
>  functions that do not take any parameters, which has been
>  corrected.
> 
>  Will merge to 'master'.

... also found its way into maint; This would make it easier for me to
backport fixes (as I started to rely on DEVELOPER=1 to warn about issues).

Thanks,
Dscho

  parent reply	other threads:[~2016-07-02 11:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-01 23:50 What's cooking in git.git (Jul 2016, #01; Fri, 1) Junio C Hamano
2016-07-02  7:59 ` Johannes Schindelin
2016-07-02 11:09 ` Johannes Schindelin [this message]
2016-07-06 14:41   ` Junio C Hamano
2016-07-06 15:32     ` Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.20.1607021306320.12947@virtualbox \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).