public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Joshua Lock <joshuagloe@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Fix oe.path.copyhardlinktree()
Date: Mon,  5 Sep 2016 14:35:08 +0100	[thread overview]
Message-ID: <cover.1473064318.git.joshua.g.lock@intel.com> (raw)

My recent change to preserve extended attributes in oe.path resulted in a
copyhardlinktree() being broken when the source contains hidden files.

This series includes a fix for copyhardlinktree() and a simple selftest for 
copyhardlinktree() which ensures the source and destination have the same number
of files after a copy.

The following changes since commit 9b08503eabf78bc1b114416523b41dcce3449f58:

  toaster: fire TaskArtifacts event (2016-09-04 00:05:13 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib joshuagl/copyhard
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=joshuagl/copyhard

Joshua Lock (2):
  oe.path: fix copyhardlinktree()
  selftest/liboe: add a test for copyhardlinktree()

 meta/lib/oe/path.py             |  9 ++++++---
 meta/lib/oeqa/selftest/liboe.py | 29 +++++++++++++++++++++++++++++
 2 files changed, 35 insertions(+), 3 deletions(-)

-- 
2.7.4


             reply	other threads:[~2016-09-05 13:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-05 13:35 Joshua Lock [this message]
2016-09-05 13:35 ` [PATCH 1/2] oe.path: fix copyhardlinktree() Joshua Lock
2016-09-05 13:35 ` [PATCH 2/2] selftest/liboe: add a test for copyhardlinktree() Joshua Lock

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.1473064318.git.joshua.g.lock@intel.com \
    --to=joshuagloe@gmail.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