From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] e2fsprogs: backport a patch to fix filetype for hardlink
Date: Fri, 23 Oct 2015 04:22:03 -0700 [thread overview]
Message-ID: <cover.1445599274.git.liezhi.yang@windriver.com> (raw)
The following changes since commit 73f8a0bf3b99d480bf97e266da0fb048714b4caf:
build-appliance-image: Update to jethro head revision (2015-10-21 23:13:03 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/e2fsprogs
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/e2fsprogs
Robert Yang (1):
e2fsprogs: backport a patch to fix filetype for hardlink
...ate-hardlinks-with-the-correct-directory-.patch | 81 ++++++++++++++++++++
.../recipes-devtools/e2fsprogs/e2fsprogs_1.42.9.bb | 1 +
2 files changed, 82 insertions(+)
create mode 100644 meta/recipes-devtools/e2fsprogs/e2fsprogs/copy-in-create-hardlinks-with-the-correct-directory-.patch
--
1.7.9.5
next reply other threads:[~2015-10-23 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 11:22 Robert Yang [this message]
2015-10-23 11:22 ` [PATCH 1/1] e2fsprogs: backport a patch to fix filetype for hardlink Robert Yang
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=cover.1445599274.git.liezhi.yang@windriver.com \
--to=liezhi.yang@windriver.com \
--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