From: Jonathan Liu <net147@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] util-linux: split libsmartcols into separate sub-package
Date: Wed, 11 Mar 2015 23:56:02 +1100 [thread overview]
Message-ID: <55003B62.8010509@gmail.com> (raw)
In-Reply-To: <CAJTo0La4E4u_sG32qYY4gBQG5NvgEYOshKPKRquHeR+ZJfbZkw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 312 bytes --]
On 11/03/2015 11:55 PM, Burton, Ross wrote:
>
> On 11 March 2015 at 12:37, Jonathan Liu <net147@gmail.com
> <mailto:net147@gmail.com>> wrote:
>
> Perhaps. I don't have experience in that area.
>
>
> Just done it, will send the patch once I've eaten lunch.
>
> Ross
Thanks.
Regards,
Jonathan
[-- Attachment #2: Type: text/html, Size: 1306 bytes --]
prev parent reply other threads:[~2015-03-11 12:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 7:00 [PATCH] util-linux: split libsmartcols into separate sub-package Jonathan Liu
2015-03-11 12:31 ` Burton, Ross
2015-03-11 12:37 ` Jonathan Liu
2015-03-11 12:55 ` Burton, Ross
2015-03-11 12:56 ` Jonathan Liu [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=55003B62.8010509@gmail.com \
--to=net147@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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