Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: "Daniel Díaz" <daniel.diaz@linaro.org>
Cc: Koen Kooi <koen.kooi@linaro.org>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] base-files: resize only serial tty's in profile
Date: Thu, 23 Mar 2017 20:03:24 +0100	[thread overview]
Message-ID: <1490295804.6396.252.camel@intel.com> (raw)
In-Reply-To: <1490293700-17717-1-git-send-email-daniel.diaz@linaro.org>

On Thu, 2017-03-23 at 12:28 -0600, Daniel Díaz wrote:
> Signed-off-by: Daniel Díaz <daniel.diaz@linaro.org>

Can you extend your commit message and add an explanation of why this
change is desirable?

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.





      reply	other threads:[~2017-03-23 19:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23 18:28 [PATCH] base-files: resize only serial tty's in profile Daniel Díaz
2017-03-23 19:03 ` Patrick Ohly [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=1490295804.6396.252.camel@intel.com \
    --to=patrick.ohly@intel.com \
    --cc=daniel.diaz@linaro.org \
    --cc=koen.kooi@linaro.org \
    --cc=openembedded-core@lists.openembedded.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