From: Lei Yang <lei.yang@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH:V2] Remove the redundant "/" in base-files
Date: Mon, 7 Jan 2013 23:03:19 +0800 [thread overview]
Message-ID: <50EAE3B7.10006@windriver.com> (raw)
In-Reply-To: <1357565899.25855.13.camel@ted>
On 01/07/2013 09:38 PM, Richard Purdie wrote:
> On Mon, 2013-01-07 at 18:54 +0800, lei.yang@windriver.com wrote:
>> From: Lei Yang<lei.yang@windriver.com>
>>
>> I'm working on my virt-test,when I check this file find it has
>> redundant "/"
>>
>> Signed-off-by: Lei Yang<lei.yang@windriver.com>
>> ---
>> meta/recipes-core/base-files/base-files_3.0.14.bb | 4 ++--
>> 1 files changed, 2 insertions(+), 2 deletions(-)
> The subject line should be:
>
> base-files: Remove the redundant "/"
Thanks for this info
Lei
> with the recipe/files being changed at the start, as per the commit
> guidelines.
>
> I've fixed it this this and merged it.
>
> Cheers,
>
> Richard
>
>
>
prev parent reply other threads:[~2013-01-07 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 10:54 [PATCH:V2] Remove the redundant "/" in base-files lei.yang
2013-01-07 13:38 ` Richard Purdie
2013-01-07 15:03 ` Lei Yang [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=50EAE3B7.10006@windriver.com \
--to=lei.yang@windriver.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