From: Tom Rini <trini@konsulko.com>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Simon Glass <sjg@chromium.org>, u-boot@lists.denx.de
Subject: Re: [PATCH 3/7] README: remove NetBSD section
Date: Wed, 25 Jan 2023 17:33:24 -0500 [thread overview]
Message-ID: <Y9GuNFH4Bf5Yz20s@bill-the-cat> (raw)
In-Reply-To: <20230125181502.115003-4-heinrich.schuchardt@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 256 bytes --]
On Wed, Jan 25, 2023 at 07:14:58PM +0100, Heinrich Schuchardt wrote:
> The information in this section is outdated.
>
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-01-25 22:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 18:14 [PATCH 0/7] README: start cleanup Heinrich Schuchardt
2023-01-25 18:14 ` [PATCH 1/7] README: correct path to sandbox.rst Heinrich Schuchardt
2023-01-26 1:41 ` Simon Glass
2023-01-25 18:14 ` [PATCH 2/7] README: rework contribution advices Heinrich Schuchardt
2023-01-25 22:33 ` Tom Rini
2023-01-25 22:41 ` Simon Glass
2023-01-25 18:14 ` [PATCH 3/7] README: remove NetBSD section Heinrich Schuchardt
2023-01-25 22:33 ` Tom Rini [this message]
2023-01-25 22:41 ` Simon Glass
2023-01-25 18:14 ` [PATCH 4/7] README: replace references to CHANGELOG Heinrich Schuchardt
2023-01-25 22:33 ` Tom Rini
2023-01-26 9:03 ` Heinrich Schuchardt
2023-01-25 22:41 ` Simon Glass
2023-01-25 18:15 ` [PATCH 5/7] doc: move 'Reproducible builds' Heinrich Schuchardt
2023-01-25 22:33 ` Tom Rini
2023-01-25 22:42 ` Simon Glass
2023-01-25 18:15 ` [PATCH 6/7] README: remove section 'Versioning' Heinrich Schuchardt
2023-01-25 22:33 ` Tom Rini
2023-01-25 22:41 ` Simon Glass
2023-01-25 18:15 ` [PATCH 7/7] doc: move directory hierarchy to HTML Heinrich Schuchardt
2023-01-25 22:33 ` Tom Rini
2023-01-25 22:41 ` Simon Glass
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=Y9GuNFH4Bf5Yz20s@bill-the-cat \
--to=trini@konsulko.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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.