From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>,
Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [master][PATCH] devtool: Add --remove-work option for devtool reset command
Date: Wed, 09 Oct 2019 15:02:37 +1300 [thread overview]
Message-ID: <2401250.Mp7qUkyezG@linux.fritz.box> (raw)
In-Reply-To: <CAMKF1sp+NJk26a5Rzav3ZxCfGSsZt-6SuiBPt+VYjMymkJtdmg@mail.gmail.com>
On Wednesday, 9 October 2019 6:39:34 AM NZDT Khem Raj wrote:
> On Tue, Oct 8, 2019 at 10:37 AM Peter Kjellerstedt <
> peter.kjellerstedt@axis.com> wrote:
>
> > > -----Original Message-----
> > > From: openembedded-core-bounces@lists.openembedded.org <openembedded-
> > > core-bounces@lists.openembedded.org> On Behalf Of Chandana Kalluri
> > > Sent: den 8 oktober 2019 04:14
> > > To: Paul Eggleton <paul.eggleton@linux.intel.com>
> > > Cc: Patches and discussions about the oe-core layer <openembedded-
> > > core@lists.openembedded.org>
> > > Subject: Re: [OE-core] [OE-Core][master][PATCH] devtool: Add --remove-
> > > work option for devtool reset command
> > >
> > > Hi Paul,
> > >
> > > Any thoughts on implementing this as a separate command as suggested
> > > by Khem?
> >
> > For what it's worth, I think the original suggested solution with a new
> > option to the existing `devtool reset` and `devtool finish` commands is
> > the better one.
>
>
> Yeah thinking about it again we already have two commands which would need
> same functionality it’s not good to introduce a third one although I think
> the usability of current solution will be a bit nicer if it was independent
> option
devtool reset does have a -a option:
--all, -a Reset all recipes (clear workspace)
It won't delete anything that no longer corresponds to a recipe in the
workspace (i.e. previously reset/finished), but is that the issue that people
are trying to solve here?
(I could see the utility of having an option to completely remove the
workspace and everything in it - I've had to write a script to do that to save
time for running the devtool oe-selftest tests for example, but I don't know
how common that use case actually is for others.)
Cheers
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2019-10-09 2:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 18:35 [master][PATCH] devtool: Add --remove-work option for devtool reset command Sai Hari Chandana Kalluri
2019-10-07 18:39 ` Khem Raj
2019-10-08 2:14 ` Chandana Kalluri
2019-10-08 17:37 ` Peter Kjellerstedt
2019-10-08 17:39 ` Khem Raj
2019-10-09 2:02 ` Paul Eggleton [this message]
2019-10-09 2:03 ` Paul Eggleton
-- strict thread matches above, loose matches on Subject: below --
2019-10-04 22:52 Sai Hari Chandana Kalluri
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=2401250.Mp7qUkyezG@linux.fritz.box \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
--cc=raj.khem@gmail.com \
/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