From: Jody Bruchon <jody@jodybruchon.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: Major changes; please cherry-pick patches since 2020-02-05 and re-submit
Date: Thu, 20 Feb 2020 12:59:04 -0500 [thread overview]
Message-ID: <40268431-d13c-ef4c-297d-d56563fa272f@jodybruchon.com> (raw)
Greetings, friends. This message is to clear up any confusion regarding
what happened to the ELKS repository and where we go from here.
The elks-org organization on Github has been deleted. The project repo
has been restored to my original location:
https://github.com/jbruchon/elks
I have force-pushed my version of the repo from February 5, 2020. Please
cherry-pick and re-submit (as a pull request on Github) all of your
patches since then for individual consideration, along with the
rationale for acceptance of the patch. An issue has been opened on the
project with this same request. I will be reviewing and approving all
pull requests myself for the foreseeable future.
I apologize for the inconvenience that I know this will cause. This
change in project management is not up for discussion and I will not
entertain any attempts to discuss it. Those who disagree with it are
free to fork the project and go their own way. All contributions are
very welcome, but you will all have to check your egos and attitudes at
the door.
Thanks to everyone for your past, present, and hopefully future support
of this project.
Administrative notes: I'm re-subscribed to this mailing list, so please
do not CC me in replies to the list. Discussion on the project issue
tracker is the preferred method of collaboration. That is all.
Best regards,
Jody Bruchon
reply other threads:[~2020-02-20 17:59 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=40268431-d13c-ef4c-297d-d56563fa272f@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).