All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Konno <joe.konno at linux.intel.com>
To: powertop@lists.01.org
Subject: [Powertop] [PATCH 0/3 v1] Rewrite README, and contribution guide
Date: Mon, 04 May 2020 09:50:11 -0700	[thread overview]
Message-ID: <20200504165014.6409-1-joe.konno@linux.intel.com> (raw)

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

From: Joe Konno <joe.konno(a)intel.com>

This series rewrites the README using markdown syntax and adds a
contribution guide.

Series was submitted as a GitHub pull request as well:
  * https://github.com/fenrus75/powertop/pull/43

Thanks to my colleague, Doug Martin, for reviewing these changes.

CONTRIBUTE.md changes up development workflows in (hopefully) a good
way. In my opinion, these are the key take-aways from that document:
  * Use GitHub workflows for sharing/collaborating (e.g. PRs, Issues)
  * Use the Linux kernel coding style

The README and CONTRIBUTE documents will continue to evolve, but this
should get us going in the right direction.

PS: PowerTOP's project description on GitHub ("please post patches to
the mailing list instead of using github pull requests") will be changed
after this series is merged-- if it is.


Joe Konno (3):
  README.md: rename, add md syntax, and major tweaks
  README.md: Fix a misspelled name
  Add CONTRIBUTE.md

 CONTRIBUTE.md | 188 ++++++++++++++++++++++++++++++++++++++++++++++
 README        | 157 --------------------------------------
 README.md     | 204 ++++++++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 392 insertions(+), 157 deletions(-)
 create mode 100644 CONTRIBUTE.md
 delete mode 100644 README
 create mode 100644 README.md

-- 
2.26.2

                 reply	other threads:[~2020-05-04 16:50 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=20200504165014.6409-1-joe.konno@linux.intel.com \
    --to=powertop@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.