From: ChenQi <Qi.Chen@windriver.com>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: OE Core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] opkg-utils: fix double slash problem in update-alternatives
Date: Fri, 21 Nov 2014 18:14:36 +0800 [thread overview]
Message-ID: <546F108C.7000304@windriver.com> (raw)
In-Reply-To: <CANyK_8c8Wo3iaKtKe0tFMcQsA-+gz2M96eMbcyBw==FVo80nzw@mail.gmail.com>
On 11/21/2014 05:59 PM, Paul Barker wrote:
> On 21 November 2014 08:50, Chen Qi <Qi.Chen@windriver.com> wrote:
>> When using update-alternatives, we would get output like the following:
>> update-alternatives: Linking //usr/bin/sh to /usr/bin/bash
>>
>> What we really want is:
>> update-alternatives: Linking /usr/bin/sh to /usr/bin/bash
>>
>> This patch fixes the above problem.
>>
>> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> opkg-utils is part of Yocto Project. Could you submit this as a change
> to opkg-utils itself and then send a SRCREV update for oe-core?
> Submission guidelines are under "Submitting patches for review" in
> the CONTRIBUTING file in opkg-utils
> (http://git.yoctoproject.org/cgit/cgit.cgi/opkg-utils/tree/CONTRIBUTING).
>
> The patch looks pretty straightforward so I should be able to give it
> a quick test and merge it to opkg-utils early next week.
>
> Cheers,
>
Hi Paul,
I've followed the link and sent out the patch.
Thanks a lot.
Best Regards,
Chen Qi
prev parent reply other threads:[~2014-11-21 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 8:50 [PATCH 0/1] opkg-utils: fix double slash problem in update-alternatives Chen Qi
2014-11-21 8:50 ` [PATCH 1/1] " Chen Qi
2014-11-21 9:59 ` Paul Barker
2014-11-21 10:14 ` ChenQi [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=546F108C.7000304@windriver.com \
--to=qi.chen@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul@paulbarker.me.uk \
/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