From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
loeliger-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
David Gibson
<david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
Subject: [PATCH 0/4] Updates to README file
Date: Thu, 28 Jul 2022 17:53:44 +1000 [thread overview]
Message-ID: <20220728075348.174412-1-david@gibson.dropbear.id.au> (raw)
The README for dtc and libfdt is fairly overdue for an update.
Reformat it in a more modern way, and add some important information
to it.
David Gibson (4):
Convert README to README.md
Remove Jon Loeliger from maintainers list
Split out information for contributors to CONTRIBUTING.md
Add description of Signed-off-by lines
CONTRIBUTING.md | 79 ++++++++++++++++++++++++++++++++++++
README | 106 ------------------------------------------------
README.md | 100 +++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 179 insertions(+), 106 deletions(-)
create mode 100644 CONTRIBUTING.md
delete mode 100644 README
create mode 100644 README.md
--
2.37.1
next reply other threads:[~2022-07-28 7:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 7:53 David Gibson [this message]
[not found] ` <20220728075348.174412-1-david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
2022-07-28 7:53 ` [PATCH 1/4] Convert README to README.md David Gibson
2022-07-28 7:53 ` [PATCH 2/4] Remove Jon Loeliger from maintainers list David Gibson
2022-07-28 7:53 ` [PATCH 3/4] Split out information for contributors to CONTRIBUTING.md David Gibson
2022-07-28 7:53 ` [PATCH 4/4] Add description of Signed-off-by lines David Gibson
[not found] ` <20220728075348.174412-5-david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
2022-07-28 16:08 ` Uwe Kleine-König
[not found] ` <20220728160800.xiexlk52grqxre3j-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2022-07-29 2:57 ` David Gibson
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=20220728075348.174412-1-david@gibson.dropbear.id.au \
--to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=loeliger-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.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 NNTP newsgroup(s).