From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>,
"Schneider, Johannes" <JSchneider@jetter.de>
Subject: Re: [PATCH 2/6] Documentation: add chapter on Talks about barebox
Date: Wed, 26 Jan 2022 10:02:30 +0100 [thread overview]
Message-ID: <20220126090230.GF23490@pengutronix.de> (raw)
In-Reply-To: <c7a12071-176b-a5c0-be94-a7f670c2a430@pengutronix.de>
On Mon, Jan 24, 2022 at 04:21:00PM +0100, Ahmad Fatoum wrote:
> On 24.01.22 16:18, Ahmad Fatoum wrote:
>
> Argh, botched authorship on rebase. @Sascha, could you fix up
> Johannes as git author on apply if there's no v2? Thanks.
Did that while applying, thanks
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2022-01-26 9:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 15:18 [PATCH 1/6] Documentation: user: introduction: update with lore/matrix/libera info Ahmad Fatoum
2022-01-24 15:18 ` [PATCH 2/6] Documentation: add chapter on Talks about barebox Ahmad Fatoum
2022-01-24 15:21 ` Ahmad Fatoum
2022-01-26 9:02 ` Sascha Hauer [this message]
2022-01-24 15:18 ` [PATCH 3/6] commands: add missing command groups Ahmad Fatoum
2022-01-24 15:18 ` [PATCH 4/6] Documentation: regulator: reference new directory from index Ahmad Fatoum
2022-01-24 15:18 ` [PATCH 5/6] Documentation: boards: openrisc: fix wrong header format Ahmad Fatoum
2022-01-24 15:18 ` [PATCH 6/6] Documentation: user: watchdog: note new wd -x option Ahmad Fatoum
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=20220126090230.GF23490@pengutronix.de \
--to=sha@pengutronix.de \
--cc=JSchneider@jetter.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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