From abhishekkmr18 at gmail.com Tue Feb 2 03:23:44 2016 From: abhishekkmr18 at gmail.com (Abhishek Kumar) Date: Tue, 2 Feb 2016 15:53:44 +0530 Subject: [Machinery] GSoC 2016 Query engine for system descriptions Message-ID: Hello I am Abhishek Kumar a student from India interested in working on Machinery project in GSoC 2016,I have coded in ruby previously and have basic proficiency in Go.I've already forked project and installed machinery.Please help me with some easy bugs and how to start with Machinery project. Thanks Abhishek -------------- next part -------------- An HTML attachment was scrubbed... URL: From fteodori at suse.com Wed Feb 3 09:39:10 2016 From: fteodori at suse.com (Federica Teodori) Date: Wed, 3 Feb 2016 17:39:10 +0100 Subject: [Machinery] GSoC 2016 Query engine for system descriptions In-Reply-To: References: Message-ID: <56B22D2E.5050602@suse.com> Hi Abhishek, On 02/02/2016 11:23 AM, Abhishek Kumar wrote: > I am Abhishek Kumar a student from India interested in working on > Machinery project in GSoC 2016,I have coded in ruby previously and have > basic proficiency in Go.I've already forked project and installed > machinery.Please help me with some easy bugs and how to start with > Machinery project. First of all, welcome! We're glad to have awaken your interest. Give us few days to discuss this internally in order to decide how to best bootstrap the whole, and we'll get back to you with some additional information. In the while, feel free to explore as much as you like the open issues [1] and the contributing guidelines [2] [1] https://github.com/SUSE/machinery/issues [2] https://github.com/SUSE/machinery/blob/master/CONTRIBUTING.md Best, Federica From cschum at suse.de Mon Feb 15 10:22:03 2016 From: cschum at suse.de (Cornelius Schumacher) Date: Mon, 15 Feb 2016 18:22:03 +0100 Subject: [Machinery] Scopes In-Reply-To: <1d2fbaf688e44b08818650e380874ea0@WHQWEX02.tyson.com> References: <1d2fbaf688e44b08818650e380874ea0@WHQWEX02.tyson.com> Message-ID: <3935090.hMdOQge78o@e82> On Montag, 15. Februar 2016 17:09:06 CET Swartz, Patrick wrote: > > Is it possible to combine scopes during inspect/compare? > This cmd ---- machinery inspect nasa17 -s users -s groups --- only did the > groups, guessing cuz it was listed last. You can provide a list of scopes as comma-separated list, such as machinery inspect nasa17 -s users,groups This should do the trick. -- Cornelius Schumacher From Patrick.Swartz at tyson.com Mon Feb 15 10:47:31 2016 From: Patrick.Swartz at tyson.com (Swartz, Patrick) Date: Mon, 15 Feb 2016 17:47:31 +0000 Subject: [Machinery] Scopes In-Reply-To: <3935090.hMdOQge78o@e82> References: <1d2fbaf688e44b08818650e380874ea0@WHQWEX02.tyson.com> <3935090.hMdOQge78o@e82> Message-ID: Ahh... Many thanks!! That works. Patrick H Swartz -----Original Message----- From: machinery-bounces at lists.suse.com [mailto:machinery-bounces at lists.suse.com] On Behalf Of Cornelius Schumacher Sent: Monday, February 15, 2016 11:22 AM To: machinery at lists.suse.com Subject: Re: [Machinery] Scopes On Montag, 15. Februar 2016 17:09:06 CET Swartz, Patrick wrote: > > Is it possible to combine scopes during inspect/compare? > This cmd ---- machinery inspect nasa17 -s users -s groups --- only did the > groups, guessing cuz it was listed last. You can provide a list of scopes as comma-separated list, such as machinery inspect nasa17 -s users,groups This should do the trick. -- Cornelius Schumacher _______________________________________________ Machinery mailing list Machinery at lists.suse.com http://lists.suse.com/mailman/listinfo/machinery ---------------------------------------------------------------------- This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email.