From: Joshua Lock <josh@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] Joshua Lock : packaged-staging: enhancements from Poky for fetching and relocatability
Date: Tue, 06 Apr 2010 15:35:28 +0100 [thread overview]
Message-ID: <1270564528.9623.19.camel@localhost.localdomain> (raw)
In-Reply-To: <1270160485.6277.143.camel@trini-m4400>
On Thu, 2010-04-01 at 15:21 -0700, Tom Rini wrote:
> On Thu, 2010-04-01 at 13:44 +0000, git version control wrote:
> > Module: openembedded.git
> > Branch: rpurdie/work-in-progress
> > Commit: ccbb586b3cfdc723ccad73dd71d85f6d41f0e6a3
> > URL: http://gitweb.openembedded.net/?p=openembedded.git&a=commit;h=ccbb586b3cfdc723ccad73dd71d85f6d41f0e6a3
> >
> > Author: Joshua Lock <josh@linux.intel.com>
> > Date: Wed Mar 31 11:22:02 2010 +0100
> >
> > packaged-staging: enhancements from Poky for fetching and relocatability
>
> Question. Do we really want to rename DEPLOY_DIR_PSTAGE to PSTAGE_DIR.
> Is that really a nomenclature change like that? I see it's still soft
> assign so outsideof TMPDIR can work still, so it's fine otherwise. Just
> checking.
>
I changed the name because we now have two pstage directories and wanted
the change to be apparent and I dropped the DEPLOY_ prefix as I moved
the default location outside of the deploy dir.
Does that seem reasonable?
Cheers,
Joshua
--
Joshua Lock
Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-04-06 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1NxKhE-0007AF-AE@melo.openembedded.org>
2010-04-01 22:21 ` [oe-commits] Joshua Lock : packaged-staging: enhancements from Poky for fetching and relocatability Tom Rini
2010-04-06 14:35 ` Joshua Lock [this message]
2010-04-06 15:09 ` Tom Rini
2010-04-06 15:25 ` Chris Larson
2010-04-06 16:22 ` Joshua Lock
2010-04-06 17:21 ` Tom Rini
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=1270564528.9623.19.camel@localhost.localdomain \
--to=josh@linux.intel.com \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.