From: Jonathan Liu <net147@gmail.com>
To: Phil Blundell <pb@pbcl.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] populate-volatile.sh: normalize repeated leading slashes in TNAME
Date: Mon, 20 May 2013 19:23:35 +1000 [thread overview]
Message-ID: <5199EB97.50900@gmail.com> (raw)
In-Reply-To: <1369041556.6920.182.camel@phil-desktop.brightsign>
On 20/05/2013 7:19 PM, Phil Blundell wrote:
> On Mon, 2013-05-20 at 11:29 +1000, Jonathan Liu wrote:
>> - TNAME=${ROOT_DIR}/${TNAME}
>> + TNAME=`echo ${ROOT_DIR}/${TNAME} | sed -e 's@^//*@/@'`
> Why is this a good thing? Your commit message is rather terse.
>
> p.
It reduces the size of /etc/volatile.cache.
Otherwise for example if you have ROOT_DIR=/, TNAME=/var/log, TNAME
becomes ///var/log.
Also if you have verbose mode enabled it actually prints out the extra
unnecessary leading slashes.
Regards,
Jonathan
next prev parent reply other threads:[~2013-05-20 9:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 1:29 [PATCH] populate-volatile.sh: normalize repeated leading slashes in TNAME Jonathan Liu
2013-05-20 9:19 ` Phil Blundell
2013-05-20 9:23 ` Jonathan Liu [this message]
2013-05-20 9:38 ` Phil Blundell
2013-05-20 10:00 ` Jonathan Liu
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=5199EB97.50900@gmail.com \
--to=net147@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.net \
/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