Re: [coreboot] Proposal: Removing obsolete & EOL boards and chipsets for 4.2 release

2015-10-28 13:59 GMT+01:00 Vladimir : > If the AGESA boards will be ported to a native init, they will be able to > continue to be supported by a master branch! That approach will allow > coreboot developers with AMD boards to avoid spending time on backporting > the

Re: [coreboot] Proposal: Removing obsolete & EOL boards and chipsets for 4.2 release

On Wed, Oct 28, 2015 at 7:59 AM, Vladimir wrote: > On 10/28/2015 04:56 AM, Alex Gagniuc wrote: >> >> How will moving [AGESA] code [to a separate branch] affect supported [AMD] >> boards? >> > > The biggest problem here is: > > Various improvements and important bug

Re: [coreboot] Proposal: Removing obsolete & EOL boards and chipsets for 4.2 release

On Wed, Oct 28, 2015 at 3:32 AM, Patrick Georgi wrote: > 2015-10-28 4:56 GMT+01:00 Alex G. : >> Here's a list of things I think should be moved to branches, right after >> the 4.2 release: > So far the idea was to drop things in master after a release,

Re: [coreboot] Proposal: Removing obsolete & EOL boards and chipsets for 4.2 release

2015-10-28 14:50 GMT+01:00 Aaron Durbin : > That presupposes there is work going on in those branches that is > desired to be pushed back into another branch. Anyone can very much > port forward something if they so choose. That's the point of the > branching mechanism. > >

Re: [coreboot] Proposal: Removing obsolete & EOL boards and chipsets for 4.2 release

On Wed, Oct 28, 2015 at 9:15 AM, Patrick Georgi wrote: > 2015-10-28 14:50 GMT+01:00 Aaron Durbin : >> That presupposes there is work going on in those branches that is >> desired to be pushed back into another branch. Anyone can very much >> port forward

Re: [coreboot] Proposal: Removing obsolete & EOL boards and chipsets for 4.2 release

Hello Alex, I totally agree with your mail. This certainly looks like the way to deal with it. We don't loose anything but make it easier to move forward with new designs at the same time when using branches. BR Wim. -Original Message- From: coreboot

Re: [coreboot] Proposal: Removing obsolete & EOL boards and chipsets for 4.2 release

It seems that we've got more issues than we can address before the proposed 4.2 release date within the next few days - we're trying to get this out in October. Maybe it's time for another 'Major' release where we can remove more than just the few mainboards and truly obsolete code that I was

Re: [coreboot] Proposal: Removing obsolete & EOL boards and chipsets for 4.2 release

IIRC I did the IBM e325/6 back in the day and I'm happy to see it die. ron On Wed, Oct 28, 2015 at 8:49 AM Martin Roth wrote: > It seems that we've got more issues than we can address before the > proposed 4.2 release date within the next few days - we're trying to > get

Re: [coreboot] Proposal: Removing obsolete & EOL boards and chipsets for 4.2 release

* Aaron Durbin [151028 14:52]: > > Various improvements and important bug fixes, that will be introduced to a > > master branch and affect all the coreboot boards, will not be automatically > > applied to that separate AMD branch. Those coreboot developers which have > > AMD

Re: [coreboot] Proposal: Removing obsolete & EOL boards and chipsets for 4.2 release

On 10/28/2015 07:00 AM, Peter Stuge wrote: > Patrick Georgi wrote: >> branches are where commits are pushed to die. > > Yes, this is a very important point, and is why I don't support Alex' > proposal of moving some things to live only on a branch, and not on master. So, tagging and removing

Re: [coreboot] Proposal: Removing obsolete & EOL boards and chipsets for 4.2 release

Alex G. wrote: > >> branches are where commits are pushed to die. > > > > Yes, this is a very important point, and is why I don't support Alex' > > proposal of moving some things to live only on a branch, and not on master. > > So, tagging and removing is better than a branch where people can >