From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] gfs2-utils.git moving on Feb 3
Date: Tue, 31 Jan 2017 15:15:50 +0000 [thread overview]
Message-ID: <4bbe1df1-35a2-e145-d3ec-d34f91c20d67@redhat.com> (raw)
Hi,
This is a heads-up that from Friday February 3 the gfs2-utils git
repository will be hosted on Pagure. We are migrating it away from
Fedora Hosted as that service is due to be discontinued at the end of
February.
The gfs2-utils git repository on Pagure <https://pagure.io/gfs2-utils>
has already been set up and currently mirrors the repository at Fedora
Hosted, so it is possible to migrate your gfs2-utils clones today if you
do not intend to push. To switch your trees over, change your remote
entry in .git/config to resemble the following:
[remote "origin"]
url = https://pagure.io/gfs2-utils.git
fetch = +refs/heads/*:refs/remotes/origin/*
On Friday those with push access will need to use
ssh://git at pagure.io/gfs2-utils.git as the "url". I recommend using it as
an additional "pushurl" with newer versions of git as it means auth is
not required when fetching. An ssh key in your Pagure user settings will
be required in order to push. This can be tested using "git push --dry-run".
Release tarballs will now be accessible at
https://releases.pagure.org/gfs2-utils/ and I will request redirects to
be set up from the Fedora Hosted project in due course.
Regards,
Andy
next reply other threads:[~2017-01-31 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 15:15 Andrew Price [this message]
2017-02-03 18:57 ` [Cluster-devel] gfs2-utils.git moving on Feb 3 Andrew Price
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=4bbe1df1-35a2-e145-d3ec-d34f91c20d67@redhat.com \
--to=anprice@redhat.com \
/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).