From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-core@lists.openembedded.org
Cc: Martin Jansa <martin.jansa-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH 3/5] scripts/sstate-sysroot-cruft.sh: add simple script to find files in sysroots not tracked by sstate
Date: Wed, 05 Dec 2012 20:04:47 +0100 [thread overview]
Message-ID: <lyehj48gmo.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <8184c008606ece423da0122a9fa6087509dfa0f5.1354731942.git.Martin.Jansa@gmail.com> (Martin Jansa's message of "Wed, 5 Dec 2012 19:26:05 +0100")
Martin Jansa <martin.jansa-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
writes:
> +WHITELIST="\/var\/pseudo\/*[^\/]*$ \/shlibs$ \.pyc$ \.pyo$"
Is it really wanted that this matches paths like '/var/pseudosomepath'?
Enrico
next prev parent reply other threads:[~2012-12-05 19:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 18:26 [PATCH 0/5] Small fixes from bitbake world Martin Jansa
2012-12-05 18:26 ` [PATCH 1/5] at: change initscript dependency from build time to runtime Martin Jansa
2012-12-05 18:26 ` [PATCH 2/5] scripts/sstate-diff-machines.sh: add simple script to compare sstate checksums between MACHINEs Martin Jansa
2012-12-05 18:26 ` [PATCH 3/5] scripts/sstate-sysroot-cruft.sh: add simple script to find files in sysroots not tracked by sstate Martin Jansa
2012-12-05 19:04 ` Enrico Scholz [this message]
2012-12-05 19:35 ` Martin Jansa
2012-12-05 22:49 ` Enrico Scholz
2012-12-06 4:30 ` Martin Jansa
2012-12-06 10:41 ` Enrico Scholz
[not found] ` <cover.1354737450.git.Martin.Jansa@gmail.com>
2012-12-05 19:59 ` [PATCHv2 " Martin Jansa
2012-12-05 19:59 ` [PATCHv2 4/5] git: fix unpackaged python files Martin Jansa
2012-12-05 18:26 ` [PATCH " Martin Jansa
2012-12-05 19:05 ` Martin Jansa
2012-12-05 18:26 ` [PATCH 5/5] python-smartpm: don't try to remove /usr/share/share twice Martin Jansa
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=lyehj48gmo.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=martin.jansa-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--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