Re: [OE-core] [PATCH] distrodata: function to identify new packages on a release

2017-08-06 Thread Tan, Shen Joon
: function to identify new packages on a release On 28 July 2017 at 23:59, Andre McCurdy <armccu...@gmail.com<mailto:armccu...@gmail.com>> wrote: > +git remote add -f origin > git://git.yoctoproject.org/poky.git<http://git.yoctoproject.org/poky.git> Is this patch inte

Re: [OE-core] [PATCH] distrodata: function to identify new packages on a release

2017-07-29 Thread Burton, Ross
On 28 July 2017 at 23:59, Andre McCurdy wrote: > > +git remote add -f origin git://git.yoctoproject.org/poky.git > > Is this patch intended for poky? Or should this be fetching oe-core and > bitbake? Seems to me that if the script were to use the current clone and just

Re: [OE-core] [PATCH] distrodata: function to identify new packages on a release

2017-07-28 Thread Andre McCurdy
On Thu, Jul 27, 2017 at 11:32 PM, Tan Shen Joon wrote: > Identify new packages based on two distinct branches. This > script takes 2 parameters; either a commit-ish or a branch > name > > To run : distrocompare.sh > E.g. distrocompare.sh morty 92aa0e7 > E.g.

[OE-core] [PATCH] distrodata: function to identify new packages on a release

2017-07-28 Thread Tan Shen Joon
Identify new packages based on two distinct branches. This script takes 2 parameters; either a commit-ish or a branch name To run : distrocompare.sh E.g. distrocompare.sh morty 92aa0e7 E.g. distrocompare.sh morty pyro output : The script will produce a file ending with new_recipe_list.txt