linux-8086.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jody Bruchon <jody@jodybruchon.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: More changes to the repo
Date: Thu, 20 Feb 2020 20:35:46 -0500	[thread overview]
Message-ID: <8975c7da-ef0b-03f3-11ad-7c88b015fb9c@jodybruchon.com> (raw)

It was suggested that it would be easier to cherry-pick out rather than 
cherry-pick back in, so I force-pushed back the Feb 20 HEAD.

I also discovered that a "limit interaction to collaborators only" 
feature was turned on, and since I deleted all collaborators and didn't 
know this was on, no one could post anything at all. I turned the option 
off, so now everyone should be able to work again. Sorry for the 
trouble. I had no idea that this "mute everyone" option even existed. 
That would explain why I've been getting notifications from fork issue 
trackers but no replies on the main one.

To be clear, no one has been blocked, banned, restricted, or whatever 
else, so if you are having problems interacting with the Github repo, 
please contact me directly and tell me what is happening.

                 reply	other threads:[~2020-02-21  1:35 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=8975c7da-ef0b-03f3-11ad-7c88b015fb9c@jodybruchon.com \
    --to=jody@jodybruchon.com \
    --cc=linux-8086@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).