-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/31/2011 11:07 AM, Denys Dmytriyenko wrote:
> Tom,
>
> Please pull these 8 commits for the external Angstrom toolchain fix,
> qt4 security advisory fix, as well as for addition of new TI machines.
> All are cherry picked from oe.dev
>
> The mach
2011/3/31 Tom Rini :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 03/31/2011 03:51 AM, Frans Meulenbroeks wrote:
>
>> Adding new machines on a maintenance branch seems somewhat odd as new
>> somewhat conflicts with maintenance.
>> is this what we want? And if so, what about adding new r
On Thu, Mar 31, 2011 at 09:44:52AM -0700, Tom Rini wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 03/31/2011 02:10 AM, Koen Kooi wrote:
> > On 31-03-11 09:45, Denys Dmytriyenko wrote:
> >> Tom,
> >
> >> Please pull these 8 commits for the external Angstrom toolchain fix,
> >> qt4
Tom,
Please pull these 8 commits for the external Angstrom toolchain fix,
qt4 security advisory fix, as well as for addition of new TI machines.
All are cherry picked from oe.dev
The machine commits were reordered to add kernel and u-boot recipes before the
actual machine configs.
Pull URL: gi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/31/2011 03:51 AM, Frans Meulenbroeks wrote:
> Adding new machines on a maintenance branch seems somewhat odd as new
> somewhat conflicts with maintenance.
> is this what we want? And if so, what about adding new recipes?
To be clear, I do not h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/31/2011 02:10 AM, Koen Kooi wrote:
> On 31-03-11 09:45, Denys Dmytriyenko wrote:
>> Tom,
>
>> Please pull these 8 commits for the external Angstrom toolchain fix,
>> qt4 security advisory fix, as well as for addition of new TI machines.
>> All a
Frans,
Before this spins into a long thread of who did what to who, let's try
reinterpreting Koen's answer;
The pull request is in line with the policy from this branch defined in
the wiki. Also, prior requests have also added new machines.
If you disagree with the policies that this branch
2011/3/31 Koen Kooi :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 31-03-11 12:51, Frans Meulenbroeks wrote:
>> Adding new machines on a maintenance branch seems somewhat odd as new
>> somewhat conflicts with maintenance.
>> is this what we want? And if so, what about adding new recipes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31-03-11 12:51, Frans Meulenbroeks wrote:
> Adding new machines on a maintenance branch seems somewhat odd as new
> somewhat conflicts with maintenance.
> is this what we want? And if so, what about adding new recipes?
Since you aren't using, devel
Adding new machines on a maintenance branch seems somewhat odd as new
somewhat conflicts with maintenance.
is this what we want? And if so, what about adding new recipes?
Frans
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31-03-11 09:45, Denys Dmytriyenko wrote:
> Tom,
>
> Please pull these 8 commits for the external Angstrom toolchain fix,
> qt4 security advisory fix, as well as for addition of new TI machines.
> All are cherry picked from oe.dev
Merging it like t
Tom,
Please pull these 8 commits for the external Angstrom toolchain fix,
qt4 security advisory fix, as well as for addition of new TI machines.
All are cherry picked from oe.dev
Pull URL: git://arago-project.org/git/people/denix/openembedded.git
Branch: 2011.03-maintenance
Browse:
http://a
12 matches
Mail list logo
