* [PATCH 0/1] poky.conf: explicitly referenced preferred linux-yocto version @ 2011-07-25 18:05 Bruce Ashfield 2011-07-25 18:05 ` [PATCH 1/1] " Bruce Ashfield 2011-07-25 18:42 ` [PATCH 0/1] " Tom Rini 0 siblings, 2 replies; 9+ messages in thread From: Bruce Ashfield @ 2011-07-25 18:05 UTC (permalink / raw) To: richard.purdie; +Cc: poky, saul.wold Here's a similar change to the meta-yocto boards, as was done to the qemu machines in oe-core. Since referencing yocto makes more sense in this layer, I made the change in the poky.conf distro default file. As the staging of linux-yocto-3.0 showed, we should explicitly state our preferred version of linux-yocto. This prevents unvalidated changes from being forced into machines. Layers and machines are free to override this as they are updated. cc: Tom Zanussi <tom.zanussi@intel.com> The following changes since commit dfec64a66e66ad4ec94a06ad900307fb0d932b98: machine/qemu: set preferred linux-yocto kernel version (2011-07-25 10:56:46 -0400) are available in the git repository at: git://git.pokylinux.org/poky-contrib zedd/kernel-yocto http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-yocto Bruce Ashfield (1): poky.conf: explicitly referenced preferred linux-yocto version meta-yocto/conf/distro/poky.conf | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) -- 1.7.4.1 ^ permalink raw reply [flat|nested] 9+ messages in thread
* [PATCH 1/1] poky.conf: explicitly referenced preferred linux-yocto version 2011-07-25 18:05 [PATCH 0/1] poky.conf: explicitly referenced preferred linux-yocto version Bruce Ashfield @ 2011-07-25 18:05 ` Bruce Ashfield 2011-07-25 18:42 ` [PATCH 0/1] " Tom Rini 1 sibling, 0 replies; 9+ messages in thread From: Bruce Ashfield @ 2011-07-25 18:05 UTC (permalink / raw) To: richard.purdie; +Cc: poky, saul.wold As the staging of linux-yocto-3.0 showed, we should explicitly state our preferred version of linux-yocto. This prevents unvalidated changes from being forced into machines. Layers and machines are free to override this as they are updated. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> --- meta-yocto/conf/distro/poky.conf | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/meta-yocto/conf/distro/poky.conf b/meta-yocto/conf/distro/poky.conf index 1ae94a0..88b8adf 100644 --- a/meta-yocto/conf/distro/poky.conf +++ b/meta-yocto/conf/distro/poky.conf @@ -12,6 +12,8 @@ LOCALCONF_VERSION = "1" DISTRO_FEATURES_append = " largefile" +PREFERRED_VERSION_linux-yocto ?= "2.6.37+git%" + SDK_NAME = "${DISTRO}-${TCLIBC}-${SDK_ARCH}-${TARGET_ARCH}" SDKPATH = "/opt/${DISTRO}/${SDK_VERSION}" -- 1.7.4.1 ^ permalink raw reply related [flat|nested] 9+ messages in thread
* Re: [PATCH 0/1] poky.conf: explicitly referenced preferred linux-yocto version 2011-07-25 18:05 [PATCH 0/1] poky.conf: explicitly referenced preferred linux-yocto version Bruce Ashfield 2011-07-25 18:05 ` [PATCH 1/1] " Bruce Ashfield @ 2011-07-25 18:42 ` Tom Rini 2011-07-25 18:50 ` Bruce Ashfield 1 sibling, 1 reply; 9+ messages in thread From: Tom Rini @ 2011-07-25 18:42 UTC (permalink / raw) To: poky On 07/25/2011 11:05 AM, Bruce Ashfield wrote: > Here's a similar change to the meta-yocto boards, as was done > to the qemu machines in oe-core. Since referencing yocto makes > more sense in this layer, I made the change in the poky.conf > distro default file. > > As the staging of linux-yocto-3.0 showed, we should explicitly > state our preferred version of linux-yocto. This prevents unvalidated > changes from being forced into machines. Layers and machines are free > to override this as they are updated. > > cc: Tom Zanussi <tom.zanussi@intel.com> > > The following changes since commit dfec64a66e66ad4ec94a06ad900307fb0d932b98: > > machine/qemu: set preferred linux-yocto kernel version (2011-07-25 10:56:46 -0400) > > are available in the git repository at: > git://git.pokylinux.org/poky-contrib zedd/kernel-yocto > http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-yocto > > Bruce Ashfield (1): > poky.conf: explicitly referenced preferred linux-yocto version > > meta-yocto/conf/distro/poky.conf | 2 ++ > 1 files changed, 2 insertions(+), 0 deletions(-) I guess as an aside, the convention we have/had in oe.dev was DEFAULT_PREFERENCE = -1, D_P_testedmachine1 = 1, etc, etc, in the kernel recipes. -- Tom Rini Mentor Graphics Corporation ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH 0/1] poky.conf: explicitly referenced preferred linux-yocto version 2011-07-25 18:42 ` [PATCH 0/1] " Tom Rini @ 2011-07-25 18:50 ` Bruce Ashfield 2011-07-25 18:59 ` Tom Rini 0 siblings, 1 reply; 9+ messages in thread From: Bruce Ashfield @ 2011-07-25 18:50 UTC (permalink / raw) To: Tom Rini; +Cc: poky On Mon, Jul 25, 2011 at 2:42 PM, Tom Rini <tom_rini@mentor.com> wrote: > On 07/25/2011 11:05 AM, Bruce Ashfield wrote: >> Here's a similar change to the meta-yocto boards, as was done >> to the qemu machines in oe-core. Since referencing yocto makes >> more sense in this layer, I made the change in the poky.conf >> distro default file. >> >> As the staging of linux-yocto-3.0 showed, we should explicitly >> state our preferred version of linux-yocto. This prevents unvalidated >> changes from being forced into machines. Layers and machines are free >> to override this as they are updated. >> >> cc: Tom Zanussi <tom.zanussi@intel.com> >> >> The following changes since commit dfec64a66e66ad4ec94a06ad900307fb0d932b98: >> >> machine/qemu: set preferred linux-yocto kernel version (2011-07-25 10:56:46 -0400) >> >> are available in the git repository at: >> git://git.pokylinux.org/poky-contrib zedd/kernel-yocto >> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-yocto >> >> Bruce Ashfield (1): >> poky.conf: explicitly referenced preferred linux-yocto version >> >> meta-yocto/conf/distro/poky.conf | 2 ++ >> 1 files changed, 2 insertions(+), 0 deletions(-) > > I guess as an aside, the convention we have/had in oe.dev was > DEFAULT_PREFERENCE = -1, D_P_testedmachine1 = 1, etc, etc, in the kernel > recipes. I've noticed that .. and it would work here as well. I'm hesitant to maintain a set of tested machine overrides in the yocto layers, since we are at a small number now, but that number isn't guaranteed to stay small. I have enough of a pain updating SRCREVs constantly, tweaking another set of vars isn't high on my 'fun' list. I prefer to have the machines opt-in, versus maintaining a list of known good machines in a central file (I realize that the machines would/could be the ones setting the default_preference back to 1 as wel, but it is still another variable to manipulate). But am not religious about any of this :) The flip to 3.0 is sort of a special case, and typically it is just a switch I throw, since all machines are tested at once. Good comment and food for thought indeed! Cheers, Bruce > > -- > Tom Rini > Mentor Graphics Corporation > _______________________________________________ > poky mailing list > poky@yoctoproject.org > https://lists.yoctoproject.org/listinfo/poky > -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH 0/1] poky.conf: explicitly referenced preferred linux-yocto version 2011-07-25 18:50 ` Bruce Ashfield @ 2011-07-25 18:59 ` Tom Rini 2011-07-25 19:04 ` Bruce Ashfield 0 siblings, 1 reply; 9+ messages in thread From: Tom Rini @ 2011-07-25 18:59 UTC (permalink / raw) To: Bruce Ashfield; +Cc: poky On 07/25/2011 11:50 AM, Bruce Ashfield wrote: > On Mon, Jul 25, 2011 at 2:42 PM, Tom Rini <tom_rini@mentor.com> wrote: >> On 07/25/2011 11:05 AM, Bruce Ashfield wrote: >>> Here's a similar change to the meta-yocto boards, as was done >>> to the qemu machines in oe-core. Since referencing yocto makes >>> more sense in this layer, I made the change in the poky.conf >>> distro default file. >>> >>> As the staging of linux-yocto-3.0 showed, we should explicitly >>> state our preferred version of linux-yocto. This prevents unvalidated >>> changes from being forced into machines. Layers and machines are free >>> to override this as they are updated. >>> >>> cc: Tom Zanussi <tom.zanussi@intel.com> >>> >>> The following changes since commit dfec64a66e66ad4ec94a06ad900307fb0d932b98: >>> >>> machine/qemu: set preferred linux-yocto kernel version (2011-07-25 10:56:46 -0400) >>> >>> are available in the git repository at: >>> git://git.pokylinux.org/poky-contrib zedd/kernel-yocto >>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-yocto >>> >>> Bruce Ashfield (1): >>> poky.conf: explicitly referenced preferred linux-yocto version >>> >>> meta-yocto/conf/distro/poky.conf | 2 ++ >>> 1 files changed, 2 insertions(+), 0 deletions(-) >> >> I guess as an aside, the convention we have/had in oe.dev was >> DEFAULT_PREFERENCE = -1, D_P_testedmachine1 = 1, etc, etc, in the kernel >> recipes. > > I've noticed that .. and it would work here as well. I'm hesitant to > maintain a set of tested machine overrides in the yocto layers, since > we are at a small number now, but that number isn't guaranteed to > stay small. I have enough of a pain updating SRCREVs constantly, > tweaking another set of vars isn't high on my 'fun' list. > > I prefer to have the machines opt-in, versus maintaining a list of known > good machines in a central file (I realize that the machines would/could > be the ones setting the default_preference back to 1 as wel, but it is > still another variable to manipulate). But am not religious about any of this :) > > The flip to 3.0 is sort of a special case, and typically it is just a switch > I throw, since all machines are tested at once. > > Good comment and food for thought indeed! So, if you go down the D_P route, meta-$whatever has linux_testedVer.bbappend D_P = "1" in it for what it wants to opt into and the meta-yocto / oe-core recipes just stay having to track qemu machines, too. -- Tom Rini Mentor Graphics Corporation ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH 0/1] poky.conf: explicitly referenced preferred linux-yocto version 2011-07-25 18:59 ` Tom Rini @ 2011-07-25 19:04 ` Bruce Ashfield 2011-07-25 20:16 ` Tom Rini 0 siblings, 1 reply; 9+ messages in thread From: Bruce Ashfield @ 2011-07-25 19:04 UTC (permalink / raw) To: Tom Rini; +Cc: poky On Mon, Jul 25, 2011 at 2:59 PM, Tom Rini <tom_rini@mentor.com> wrote: > On 07/25/2011 11:50 AM, Bruce Ashfield wrote: >> On Mon, Jul 25, 2011 at 2:42 PM, Tom Rini <tom_rini@mentor.com> wrote: >>> On 07/25/2011 11:05 AM, Bruce Ashfield wrote: >>>> Here's a similar change to the meta-yocto boards, as was done >>>> to the qemu machines in oe-core. Since referencing yocto makes >>>> more sense in this layer, I made the change in the poky.conf >>>> distro default file. >>>> >>>> As the staging of linux-yocto-3.0 showed, we should explicitly >>>> state our preferred version of linux-yocto. This prevents unvalidated >>>> changes from being forced into machines. Layers and machines are free >>>> to override this as they are updated. >>>> >>>> cc: Tom Zanussi <tom.zanussi@intel.com> >>>> >>>> The following changes since commit dfec64a66e66ad4ec94a06ad900307fb0d932b98: >>>> >>>> machine/qemu: set preferred linux-yocto kernel version (2011-07-25 10:56:46 -0400) >>>> >>>> are available in the git repository at: >>>> git://git.pokylinux.org/poky-contrib zedd/kernel-yocto >>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-yocto >>>> >>>> Bruce Ashfield (1): >>>> poky.conf: explicitly referenced preferred linux-yocto version >>>> >>>> meta-yocto/conf/distro/poky.conf | 2 ++ >>>> 1 files changed, 2 insertions(+), 0 deletions(-) >>> >>> I guess as an aside, the convention we have/had in oe.dev was >>> DEFAULT_PREFERENCE = -1, D_P_testedmachine1 = 1, etc, etc, in the kernel >>> recipes. >> >> I've noticed that .. and it would work here as well. I'm hesitant to >> maintain a set of tested machine overrides in the yocto layers, since >> we are at a small number now, but that number isn't guaranteed to >> stay small. I have enough of a pain updating SRCREVs constantly, >> tweaking another set of vars isn't high on my 'fun' list. >> >> I prefer to have the machines opt-in, versus maintaining a list of known >> good machines in a central file (I realize that the machines would/could >> be the ones setting the default_preference back to 1 as wel, but it is >> still another variable to manipulate). But am not religious about any of this :) >> >> The flip to 3.0 is sort of a special case, and typically it is just a switch >> I throw, since all machines are tested at once. >> >> Good comment and food for thought indeed! > > So, if you go down the D_P route, meta-$whatever has > linux_testedVer.bbappend D_P = "1" in it for what it wants to opt into > and the meta-yocto / oe-core recipes just stay having to track qemu > machines, too. Understood, that's what I tried to say (badly) when I mentioned that the machines could set this variable in their own layer, versus a central update. The question that pops up for me, what's the pros and cons of this versus the machine setting a version preference by machine specific overrides (maybe they can't?) or setting their compatibility variables. I can see that this is an explicit statement of tested versus not tested, versus something more implicit. But are there others ? Cheers, Bruce > > -- > Tom Rini > Mentor Graphics Corporation > -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH 0/1] poky.conf: explicitly referenced preferred linux-yocto version 2011-07-25 19:04 ` Bruce Ashfield @ 2011-07-25 20:16 ` Tom Rini 2011-08-18 18:25 ` Darren Hart 0 siblings, 1 reply; 9+ messages in thread From: Tom Rini @ 2011-07-25 20:16 UTC (permalink / raw) To: Bruce Ashfield; +Cc: poky On 07/25/2011 12:04 PM, Bruce Ashfield wrote: > On Mon, Jul 25, 2011 at 2:59 PM, Tom Rini <tom_rini@mentor.com> wrote: >> On 07/25/2011 11:50 AM, Bruce Ashfield wrote: >>> On Mon, Jul 25, 2011 at 2:42 PM, Tom Rini <tom_rini@mentor.com> wrote: >>>> On 07/25/2011 11:05 AM, Bruce Ashfield wrote: >>>>> Here's a similar change to the meta-yocto boards, as was done >>>>> to the qemu machines in oe-core. Since referencing yocto makes >>>>> more sense in this layer, I made the change in the poky.conf >>>>> distro default file. >>>>> >>>>> As the staging of linux-yocto-3.0 showed, we should explicitly >>>>> state our preferred version of linux-yocto. This prevents unvalidated >>>>> changes from being forced into machines. Layers and machines are free >>>>> to override this as they are updated. >>>>> >>>>> cc: Tom Zanussi <tom.zanussi@intel.com> >>>>> >>>>> The following changes since commit dfec64a66e66ad4ec94a06ad900307fb0d932b98: >>>>> >>>>> machine/qemu: set preferred linux-yocto kernel version (2011-07-25 10:56:46 -0400) >>>>> >>>>> are available in the git repository at: >>>>> git://git.pokylinux.org/poky-contrib zedd/kernel-yocto >>>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-yocto >>>>> >>>>> Bruce Ashfield (1): >>>>> poky.conf: explicitly referenced preferred linux-yocto version >>>>> >>>>> meta-yocto/conf/distro/poky.conf | 2 ++ >>>>> 1 files changed, 2 insertions(+), 0 deletions(-) >>>> >>>> I guess as an aside, the convention we have/had in oe.dev was >>>> DEFAULT_PREFERENCE = -1, D_P_testedmachine1 = 1, etc, etc, in the kernel >>>> recipes. >>> >>> I've noticed that .. and it would work here as well. I'm hesitant to >>> maintain a set of tested machine overrides in the yocto layers, since >>> we are at a small number now, but that number isn't guaranteed to >>> stay small. I have enough of a pain updating SRCREVs constantly, >>> tweaking another set of vars isn't high on my 'fun' list. >>> >>> I prefer to have the machines opt-in, versus maintaining a list of known >>> good machines in a central file (I realize that the machines would/could >>> be the ones setting the default_preference back to 1 as wel, but it is >>> still another variable to manipulate). But am not religious about any of this :) >>> >>> The flip to 3.0 is sort of a special case, and typically it is just a switch >>> I throw, since all machines are tested at once. >>> >>> Good comment and food for thought indeed! >> >> So, if you go down the D_P route, meta-$whatever has >> linux_testedVer.bbappend D_P = "1" in it for what it wants to opt into >> and the meta-yocto / oe-core recipes just stay having to track qemu >> machines, too. > > Understood, that's what I tried to say (badly) when I mentioned that the > machines could set this variable in their own layer, versus a central > update. > > The question that pops up for me, what's the pros and cons of this > versus the machine setting a version preference by machine specific > overrides (maybe they can't?) or setting their compatibility variables. > I can see that this is an explicit statement of tested versus not > tested, versus something more implicit. But are there others ? To me, it boils down to where do you make the pain point. If it's in the kernel recipe (/ bbappend), we don't cause a re-parse of the metadata. It can however be arguably more of a surprise when the kernel upgrades. With my Mentor hat, we've always pinned the recipe version down for the kernel, but with my community hat, building the latest that's supposed to work feels best. -- Tom Rini Mentor Graphics Corporation ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH 0/1] poky.conf: explicitly referenced preferred linux-yocto version 2011-07-25 20:16 ` Tom Rini @ 2011-08-18 18:25 ` Darren Hart 2011-08-18 18:32 ` Paul Eggleton 0 siblings, 1 reply; 9+ messages in thread From: Darren Hart @ 2011-08-18 18:25 UTC (permalink / raw) To: Tom Rini; +Cc: poky On 07/25/2011 01:16 PM, Tom Rini wrote: > On 07/25/2011 12:04 PM, Bruce Ashfield wrote: >> On Mon, Jul 25, 2011 at 2:59 PM, Tom Rini <tom_rini@mentor.com> wrote: >>> On 07/25/2011 11:50 AM, Bruce Ashfield wrote: >>>> On Mon, Jul 25, 2011 at 2:42 PM, Tom Rini <tom_rini@mentor.com> wrote: >>>>> On 07/25/2011 11:05 AM, Bruce Ashfield wrote: >>>>>> Here's a similar change to the meta-yocto boards, as was done >>>>>> to the qemu machines in oe-core. Since referencing yocto makes >>>>>> more sense in this layer, I made the change in the poky.conf >>>>>> distro default file. >>>>>> >>>>>> As the staging of linux-yocto-3.0 showed, we should explicitly >>>>>> state our preferred version of linux-yocto. This prevents unvalidated >>>>>> changes from being forced into machines. Layers and machines are free >>>>>> to override this as they are updated. >>>>>> >>>>>> cc: Tom Zanussi <tom.zanussi@intel.com> >>>>>> >>>>>> The following changes since commit dfec64a66e66ad4ec94a06ad900307fb0d932b98: >>>>>> >>>>>> machine/qemu: set preferred linux-yocto kernel version (2011-07-25 10:56:46 -0400) >>>>>> >>>>>> are available in the git repository at: >>>>>> git://git.pokylinux.org/poky-contrib zedd/kernel-yocto >>>>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-yocto >>>>>> >>>>>> Bruce Ashfield (1): >>>>>> poky.conf: explicitly referenced preferred linux-yocto version >>>>>> >>>>>> meta-yocto/conf/distro/poky.conf | 2 ++ >>>>>> 1 files changed, 2 insertions(+), 0 deletions(-) >>>>> >>>>> I guess as an aside, the convention we have/had in oe.dev was >>>>> DEFAULT_PREFERENCE = -1, D_P_testedmachine1 = 1, etc, etc, in the kernel >>>>> recipes. >>>> >>>> I've noticed that .. and it would work here as well. I'm hesitant to >>>> maintain a set of tested machine overrides in the yocto layers, since >>>> we are at a small number now, but that number isn't guaranteed to >>>> stay small. I have enough of a pain updating SRCREVs constantly, >>>> tweaking another set of vars isn't high on my 'fun' list. >>>> >>>> I prefer to have the machines opt-in, versus maintaining a list of known >>>> good machines in a central file (I realize that the machines would/could >>>> be the ones setting the default_preference back to 1 as wel, but it is >>>> still another variable to manipulate). But am not religious about any of this :) >>>> >>>> The flip to 3.0 is sort of a special case, and typically it is just a switch >>>> I throw, since all machines are tested at once. >>>> >>>> Good comment and food for thought indeed! >>> >>> So, if you go down the D_P route, meta-$whatever has >>> linux_testedVer.bbappend D_P = "1" in it for what it wants to opt into >>> and the meta-yocto / oe-core recipes just stay having to track qemu >>> machines, too. >> >> Understood, that's what I tried to say (badly) when I mentioned that the >> machines could set this variable in their own layer, versus a central >> update. >> >> The question that pops up for me, what's the pros and cons of this >> versus the machine setting a version preference by machine specific >> overrides (maybe they can't?) or setting their compatibility variables. >> I can see that this is an explicit statement of tested versus not >> tested, versus something more implicit. But are there others ? > > To me, it boils down to where do you make the pain point. If it's in > the kernel recipe (/ bbappend), we don't cause a re-parse of the > metadata. It can however be arguably more of a surprise when the kernel > upgrades. With my Mentor hat, we've always pinned the recipe version > down for the kernel, but with my community hat, building the latest > that's supposed to work feels best. How do DEFAULT_PREFERENCE and PREFERRED_VERSION relate to each other? Does one trump the other? -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH 0/1] poky.conf: explicitly referenced preferred linux-yocto version 2011-08-18 18:25 ` Darren Hart @ 2011-08-18 18:32 ` Paul Eggleton 0 siblings, 0 replies; 9+ messages in thread From: Paul Eggleton @ 2011-08-18 18:32 UTC (permalink / raw) To: poky; +Cc: Darren Hart, Tom Rini On Thursday 18 August 2011 19:25:48 Darren Hart wrote: > How do DEFAULT_PREFERENCE and PREFERRED_VERSION relate to each other? > Does one trump the other? DEFAULT_PREFERENCE is intentionally weak (says RP) and will be overridden by PREFERRED_VERSION_packagename if the latter is specified. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2011-08-18 18:32 UTC | newest] Thread overview: 9+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2011-07-25 18:05 [PATCH 0/1] poky.conf: explicitly referenced preferred linux-yocto version Bruce Ashfield 2011-07-25 18:05 ` [PATCH 1/1] " Bruce Ashfield 2011-07-25 18:42 ` [PATCH 0/1] " Tom Rini 2011-07-25 18:50 ` Bruce Ashfield 2011-07-25 18:59 ` Tom Rini 2011-07-25 19:04 ` Bruce Ashfield 2011-07-25 20:16 ` Tom Rini 2011-08-18 18:25 ` Darren Hart 2011-08-18 18:32 ` Paul Eggleton
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.