public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE, IMPORTANT] oss.sgi.com git repository shutdown
Date: Wed, 17 Aug 2016 12:59:28 +1000	[thread overview]
Message-ID: <20160817025928.GH19025@dastard> (raw)

[-- Attachment #1: Type: text/plain, Size: 1308 bytes --]

Hi folks,

Sorry for the shouty title, but if you don't read this then things
might break unexpectedly for you. We've been given the heads up that
the future of the oss.sgi.com infrastructure is in doubt, so we're
taking steps to make sure everyone using xfstests moves off it
before it disappears into a bit bucket somewhere and we get lots of
questions about it.

As a result, I will no longer be pushing new commits to this
repository. Instead, I've just pushed a commit to the oss.sgi.com
xfstests repository that will not appear in the repository on
kernel.org.  This commit essentially breaks xfstests in several
different ways - any attempt to run check, make, install, etc will
result in a message such as:

$ ./check
The repository at oss.sgi.com is no longer used.
Please change your sources to point at:

	git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git

and refetch the your master branch.
$

If you see this message, the action you need to take should be
pretty obvious. That is, update the origin of your repositories to
point to:

git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git

and force update your master branch to get rid of the "break it all"
commit that was pulled from oss.sgi.com.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

                 reply	other threads:[~2016-08-17  3:24 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=20160817025928.GH19025@dastard \
    --to=david@fromorbit.com \
    --cc=fstests@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