linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill O'Donnell <billodo@redhat.com>
To: linux-xfs@vger.kernel.org
Subject: [XFS SUMMIT] xfs and gcc
Date: Thu, 23 Apr 2020 10:03:06 -0500	[thread overview]
Message-ID: <20200423150306.GA345064@redhat.com> (raw)

Hello -

I'd be interested in having some discussion about the forward momentum
of gcc, and xfs staying in reasonable sync with it. I'm sure you've noticed
the warnings stacking up as xfs and xfsprogs is built. With gcc-10 coming
about in distros, the inevitable warnings and errors will become more than
annoying.

How best to approach modifications to xfs to alleviate these build issues?

Thanks-
Bill


             reply	other threads:[~2020-04-23 15:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23 15:03 Bill O'Donnell [this message]
2020-04-27 17:24 ` [XFS SUMMIT] xfs and gcc Darrick J. Wong
2020-04-28 21:01   ` Bill O'Donnell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200423150306.GA345064@redhat.com \
    --to=billodo@redhat.com \
    --cc=linux-xfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).