Hi,
On Fri, 24 Mar 2017, Sebastian Schuberth wrote:
> On Fri, Mar 24, 2017 at 1:35 PM, Lars Schneider
> wrote:
>
> >> 1. use appveyor.com, as that is a Travis-like service for Windows. We do
> >> our
> >> windows-builds in the curl project using that.
> >
> > The Git for Windows build and te
Lars Schneider writes:
> I think I addressed all issues from the v1 review (see interdiff below)
> with one exception. The script still uses bash instead of sh. Something
> about this does not work in sh:
> --output >(sed "$(printf '1s/^\xef\xbb\xbf//')" >cat >&3)
>
> Does anyone know how to
On Fri, Mar 24, 2017 at 12:37:47PM +0100, Lars Schneider wrote:
> I think I addressed all issues from the v1 review (see interdiff below)
> with one exception. The script still uses bash instead of sh. Something
> about this does not work in sh:
> --output >(sed "$(printf '1s/^\xef\xbb\xbf//')
On Fri, 24 Mar 2017, Lars Schneider wrote:
2. run your own buildbot and submit data using the regular github hook and
have buildbot submit the results back (it has a plugin that can do that).
We do solaris-builds in the curl project using that method (thanks to
opencsw.org) and some additi
On Fri, Mar 24, 2017 at 1:35 PM, Lars Schneider
wrote:
>> 1. use appveyor.com, as that is a Travis-like service for Windows. We do our
>> windows-builds in the curl project using that.
>
> The Git for Windows build and tests are *really* resources intensive and they
> take a lot of setup time.
> On 24 Mar 2017, at 12:48, Daniel Stenberg wrote:
>
> On Fri, 24 Mar 2017, Lars Schneider wrote:
>
>> Most Git developers work on Linux and they have no way to know if their
>> changes would break the Git for Windows build. Let's fix that by adding a
>> job to TravisCI that builds and tests
On Fri, 24 Mar 2017, Lars Schneider wrote:
Most Git developers work on Linux and they have no way to know if their
changes would break the Git for Windows build. Let's fix that by adding a
job to TravisCI that builds and tests Git on Windows. Unfortunately,
TravisCI does not support Windows.
Most Git developers work on Linux and they have no way to know if their
changes would break the Git for Windows build. Let's fix that by adding
a job to TravisCI that builds and tests Git on Windows. Unfortunately,
TravisCI does not support Windows.
Therefore, we did the following:
* Johannes Schi
8 matches
Mail list logo