From Jochen.Sielck at dataport.de  Tue Aug  2 02:09:09 2016
From: Jochen.Sielck at dataport.de (Sielck, Jochen)
Date: Tue, 2 Aug 2016 08:09:09 +0000
Subject: [Machinery] machinery: Phase 5
In-Reply-To: <1829092.1XAgRbIl7W@e82>
References: <99672a020dbb477589d2edefde91c47d@WCLMSPA001.dpaorvv.de>
	<1829092.1XAgRbIl7W@e82>
Message-ID: <e5592c461c6a49fdbe5ce5e3afdd8228@WCLMSPA001.dpaorvv.de>

I am most interested in the filter command implementation during inspecting to have a focused view on this within the browser. 

-----Urspr?ngliche Nachricht-----
Von: machinery-bounces at lists.suse.com [mailto:machinery-bounces at lists.suse.com] Im Auftrag von Cornelius Schumacher
Gesendet: Freitag, 29. Juli 2016 14:10
An: machinery at lists.suse.com
Betreff: Re: [Machinery] machinery: Phase 5

On Freitag, 29. Juli 2016 07:07:05 CEST Sielck, Jochen wrote:
> 
> found this hints on
> https://github.com/SUSE/machinery/blob/master/docs/Filtering-Design.md
> 
> *  Step 1: Implement core filtering classes and move current filtering 
> to them. This includes storing filters used during inspection in the 
> meta data of the system description. (done) *  Step 2: Implement 
> --skip-files option for the inspect command to make it easier for 
> users to add filters. *  Step
> 3: Implement generic --exclude option to let users add additional 
> filters on demand. This option can also be used in our integration 
> tests. (done as experimental option) *  Step 4: Implement inverted 
> filters
> *  Step 5: Implement filter command and persistent per-description filters.
> *  Step 6: Implement user-level persistent filters.
> *  Step 7: Implement disabling of filters
> 
> 
> I guess, we actually reached Step 4 .. what's the plan to reach Step 
> 5, 6, 7 ?

You are right, we are at step 4. We have plans to make the experimental option generally available as the next step.

What of the other features would you need? Are you interested in making it possible to store sets of filters as part of a description or as user-wide preference?

--
Cornelius Schumacher <cschum at suse.de>
_______________________________________________
Machinery mailing list
Machinery at lists.suse.com
http://lists.suse.com/mailman/listinfo/machinery

From jels at suse.com  Thu Aug 11 01:01:39 2016
From: jels at suse.com (Johann Els)
Date: Thu, 11 Aug 2016 01:01:39 -0600
Subject: [Machinery] Please advise how i can Subscribe?
Message-ID: <57AC3EF3020000D30004FBA5@prv1-mh.provo.novell.com>


From mschnitzer at suse.de  Fri Aug 12 01:57:53 2016
From: mschnitzer at suse.de (Manuel Schnitzer)
Date: Fri, 12 Aug 2016 09:57:53 +0200
Subject: [Machinery] Please advise how i can Subscribe?
In-Reply-To: <57AC3EF3020000D30004FBA5@prv1-mh.provo.novell.com>
References: <57AC3EF3020000D30004FBA5@prv1-mh.provo.novell.com>
Message-ID: <20160812095753.2af441a2@manuel.suse.de>

Hi,

according to the subject of this mail, I ASSUME that you'd like
to subscribe to this mailing list ;-)

Here is the link: http://lists.suse.com/mailman/listinfo/machinery

Manuel


On Thu, 11 Aug 2016 01:01:39 -0600
Johann Els <jels at suse.com> wrote:

> 
> _______________________________________________
> Machinery mailing list
> Machinery at lists.suse.com
> http://lists.suse.com/mailman/listinfo/machinery



-- 
Manuel Schnitzer, Junior Web Application Engineer, DevOps Team
SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg
Tel: +49-911-74053-0, Fax: +49-911-7417755
SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Jennifer Guild,
Graham Norton, HRB 21284 (AG N?rnberg)

GPG Fingerprint: 9D2E 219D 6B71 77A7 E666  909C 8753 CB67 DEFD C709