From: Chris PeBenito <chpebeni@linux.microsoft.com>
To: SELinux Reference Policy mailing list
<selinux-refpolicy@vger.kernel.org>
Subject: ANN: SELinux repository changes
Date: Thu, 25 May 2023 14:08:05 -0400 [thread overview]
Message-ID: <468ee32c-7fa7-1043-f9eb-9ace7fccfa87@linux.microsoft.com> (raw)
In-Reply-To: <CAHC9VhTo0LnHwfnF1kfNcosUDdB=MtBQePemR+ju81_GFSuGiA@mail.gmail.com>
-------- Forwarded Message --------
Subject: ANN: SELinux repository changes
Date: Wed, 24 May 2023 16:33:43 -0400
From: Paul Moore <paul@paul-moore.com>
To: selinux@vger.kernel.org
Hello all,
On behalf of all the various SELinux maintainers and myself, I wanted
to provide a quick update on some changes that occurred today to the
SELinux Project repositories hosted on GitHub.
* https://github.com/SELinuxProject
The first, and most noticeable change, is all of the repositories have
now changed their default branch from "master" to "main". In order to
minimize the immediate impact of the change, the "master" branch has
been preserved and locked; this should allow existing automations to
continue to function, but be warned that any new commits/PRs will be
merged into "main". You can expect the "master" branches to be
removed at a later date. For those of you with local repository
clones, you can update your repo with the following commands:
(assuming your GitHub remote is named "origin", and you are in your
"master" branch)
% git remote update origin
% git branch -m main
% git branch -u origin/main main
The commands will pull in the new remote branch definition, rename
your current "master" branch to "main", and set the current local
"main" branch to pull from the remote "origin/main" branch.
The second, and long overdue, change was to archive the CIL
repository. With CIL development moving to the main SELinux userspace
repository, and no new commits in over nine years, it was time to
deprecate the old CIL repository.
--
paul-moore.com
parent reply other threads:[~2023-05-25 18:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAHC9VhTo0LnHwfnF1kfNcosUDdB=MtBQePemR+ju81_GFSuGiA@mail.gmail.com>]
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=468ee32c-7fa7-1043-f9eb-9ace7fccfa87@linux.microsoft.com \
--to=chpebeni@linux.microsoft.com \
--cc=selinux-refpolicy@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 read-only IMAP folder(s) and NNTP newsgroup(s).