From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Johannes Schneider via lists.openembedded.org"
<johannes.schneider=leica-geosystems.com@lists.openembedded.org>
Cc: johannes.schneider@leica-geosystems.com,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
Jason Wessel <jason.wessel@windriver.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [OE-core] [meta-oe][PATCH] base-files: profile: allow profile.d to set EDITOR
Date: Sat, 14 Oct 2023 10:52:08 +0200 [thread overview]
Message-ID: <20231014105208.2d70c1a4@booty> (raw)
In-Reply-To: <DB6PR06MB400859907A9D2543961D71D5BCD2A@DB6PR06MB4008.eurprd06.prod.outlook.com>
Hello again,
On Fri, 13 Oct 2023 10:27:34 +0000
"Johannes Schneider via lists.openembedded.org"
<johannes.schneider=leica-geosystems.com@lists.openembedded.org> wrote:
> From 0013c8a6482018d5476e4eb2f4d537c96551e0c6 Mon Sep 17 00:00:00 2001
> From: Johannes Schneider <johannes.schneider@leica-geosystems.com>
> Date: Fri, 13 Oct 2023 08:28:38 +0200
> Subject: [PATCH v1] base-files: profile: allow profile.d to set EDITOR
In addition to my previous remark, I noticed that your e-mail is
formatted in an incorrect way. The From/Date/Subject: lines inside the
e-mail body suggest you probably manipulated a git-formatted patch in
an incorrect way. You should review the way you are sending patches,
perhaps you only need to call 'git send-patch -1' or similar instead of
some manipulation you have been doing here.
Again, you don't need to resend for this tome as I have fixed it
locally.
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2023-10-14 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 10:27 [meta-oe][PATCH] base-files: profile: allow profile.d to set EDITOR SCHNEIDER Johannes
2023-10-14 8:08 ` [OE-core] " Luca Ceresoli
2023-10-14 8:52 ` Luca Ceresoli [this message]
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=20231014105208.2d70c1a4@booty \
--to=luca.ceresoli@bootlin.com \
--cc=jason.wessel@windriver.com \
--cc=johannes.schneider=leica-geosystems.com@lists.openembedded.org \
--cc=johannes.schneider@leica-geosystems.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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