I'd like to get to the point where we have no or few warnings with no
warnings turned off. It sounds like that might be a while though.
Perhaps we could start with those two extra flags to quiet warnings for the
gcc8/Ubuntu-16.04 build, then think about how to do the string truncation
in a better
On Tue, Apr 23, 2019 at 08:35:12PM -0700, we recorded a bogon-computron
collision of the flavor, containing:
> Your thinking on distributions to drop is sound. It's what I would want as
> well.
>
> For the gcc-8 build should we add those two flags as well?
Perhaps, unless you really want to
Your thinking on distributions to drop is sound. It's what I would want as
well.
For the gcc-8 build should we add those two flags as well?
I just sent my .travis.yml file to Jason for incorporation. Hopefully he
can make it work with all the builds and just put gcc-8 in for the one.
On Tue,
On Tue, Apr 23, 2019 at 09:56:56PM -0500, we recorded a bogon-computron
collision of the flavor, containing:
> I can integrate it. Which build were you thinking of swapping out, or would
> this be an addition?
We should probably just drop the Ubuntu 14.04 build altogether. Ubuntu 14.04
is past
I have it building with gcc-8 on Xenial in my topic branch. Xenial is
Ubuntu-16.04. To get it to work I commented out the other builds and just
build with the new one until I could make it work properly. Now I don't
know how to integrate what I've done with the earlier 4-build .travis.yml
file we
Maybe swap the Ubuntu 14.04 max build to use gcc 8 if that is a valid
combination? The travis-ci documentation has the comment "If you are on an
open-source plan, please remember that Travis CI provides this service free
of charge to the community. So please only specify the matrix you *actually
You should definitely read and internalize "How to Git Pretty":
http://justinhileman.info/article/changing-history/
On Tue, Apr 23, 2019 at 06:57:30PM -0600, we recorded a bogon-computron
collision of the flavor, containing:
> On Tue, Apr 23, 2019 at 05:51:21PM -0700, we recorded a
On Tue, Apr 23, 2019 at 05:51:21PM -0700, we recorded a bogon-computron
collision of the flavor, containing:
> Scenario: I have a topic branch I'm working on. A pull request or a direct
> commit goes into upstream master. How should I update my topic branch?
>
> What I've been doing:
>
>
On Tue, Apr 23, 2019 at 05:39:02PM -0700, we recorded a bogon-computron
collision of the flavor, containing:
> We have Xastir building fairly cleanly on Travis-CI with three test cases:
>
> Ubuntu-14.04 max build
> Ubuntu-14.04 min build
> Ubuntu-16.04 max build
>
> Maybe what I should have
We have Xastir building fairly cleanly on Travis-CI with three test cases:
Ubuntu-14.04 max build
Ubuntu-14.04 min build
Ubuntu-16.04 max build
Maybe what I should have said is that there aren't any Xastir code
errors/warnings being shown on those three, but a few warnings appear due
to problems
10 matches
Mail list logo