On Monday 18 September 2017 12:32 AM, Phillip Wood wrote:
May be the Windows build exit with failure on other repos rather than
saying it passes?
I'm not quite sure what you're asking. If the tests aren't run it
needs to look like a pass or everyone's branches would be marked as
failing on
On 17/09/17 14:42, Kaartic Sivaraam wrote:
On Sun, 2017-09-17 at 14:24 +0100, Phillip Wood wrote:
From that commit:
diff --git a/ci/run-windows-build.sh b/ci/run-windows-build.sh
new file mode 100755
index 0..4e3a50b60
--- /dev/null
+++ b/ci/run-windows-build.sh
@@ -0,0 +1,74 @@
On Sun, 2017-09-17 at 14:24 +0100, Phillip Wood wrote:
>
> From that commit:
> diff --git a/ci/run-windows-build.sh b/ci/run-windows-build.sh
> new file mode 100755
> index 0..4e3a50b60
> --- /dev/null
> +++ b/ci/run-windows-build.sh
> @@ -0,0 +1,74 @@
> +#!/usr/bin/env bash
> +#
> +#
On 17/09/17 06:28, Kaartic Sivaraam wrote:
029aeeed5 (travis-ci: build and test Git on Windows, 2017-03-24) added
support for testing the git build for Windows.
So, update the documentation and the example used in it.
From that commit:
diff --git a/ci/run-windows-build.sh
029aeeed5 (travis-ci: build and test Git on Windows, 2017-03-24) added
support for testing the git build for Windows.
So, update the documentation and the example used in it.
Signed-off-by: Kaartic Sivaraam
---
Documentation/SubmittingPatches | 5 +++--
1 file
5 matches
Mail list logo