Hi Junio,
On Wed, 6 Jul 2016, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> > 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
Johannes Schindelin writes:
> 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.
>>
>> Wi
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 cherr
Hi,
On Fri, 1 Jul 2016, Junio C Hamano wrote:
> * jk/common-main-2.8 (2016-07-01) 5 commits
> - common-main: call git_setup_gettext()
> - common-main: call restore_sigpipe_to_default()
> - common-main: call sanitize_stdfds()
> - common-main: call git_extract_argv0_path()
> - add an extra lev
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.
The first few batches for this cyc
5 matches
Mail list logo