linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: lsf-pc@lists.linux-foundation.org
Cc: Luis Chamberlain <mcgrof@kernel.org>, linux-fsdevel@vger.kernel.org
Subject: [LSF/MM TOPIC] FS: oscheck - tracking stable/distro baselines
Date: Wed, 13 Feb 2019 13:52:31 -0800	[thread overview]
Message-ID: <20190213215231.GZ11489@garbanzo.do-not-panic.com> (raw)

I've started to give some love towards XFS stable maintenance, the first
results of that work went in v4.19.21. I'd like to review what I use to
track the stable kernel baselines, oscheck [0], to avoid regressions,
and show how this can also easily be used to track any distribution
baselines as well. I'll review how we're doing across the board on
different distributions on fstests results for XFS. I'd like to get
feedback on known issues / see if people working on knowing issues, and
finally review future work being considered.

[0] https://gitlab.com/mcgrof/oscheck

  Luis


                 reply	other threads:[~2019-02-13 21:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20190213215231.GZ11489@garbanzo.do-not-panic.com \
    --to=mcgrof@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.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).