On Thu, Oct 4, 2018 at 9:11 PM Rob Herring wrote:
>
> On Thu, Oct 4, 2018 at 3:33 AM Daniel Vetter wrote:
> >
> > On Thu, Oct 4, 2018 at 12:27 AM Rob Herring wrote:
> > >
> > > It's convenient to use Travis-CI for doing kernel builds. Doing so
> > > requires a github repo, Travis-CI enabled for
On Thu, Oct 4, 2018 at 3:33 AM Daniel Vetter wrote:
>
> On Thu, Oct 4, 2018 at 12:27 AM Rob Herring wrote:
> >
> > It's convenient to use Travis-CI for doing kernel builds. Doing so
> > requires a github repo, Travis-CI enabled for that repo, and a
> > .travis.yml file in the repository. This com
On Thu, Oct 4, 2018 at 12:27 AM Rob Herring wrote:
>
> It's convenient to use Travis-CI for doing kernel builds. Doing so
> requires a github repo, Travis-CI enabled for that repo, and a
> .travis.yml file in the repository. This commit addresses the last part.
> Each repository branch must have a
It's convenient to use Travis-CI for doing kernel builds. Doing so
requires a github repo, Travis-CI enabled for that repo, and a
.travis.yml file in the repository. This commit addresses the last part.
Each repository branch must have a .travis.yml file in order to run
Travis-CI jobs.
Obviously,
4 matches
Mail list logo
