Secondary architectures and marketing

Oliver Falk oliver at linux-kernel.at
Thu Jan 15 15:03:18 UTC 2009


Alex Deucher wrote:
> On Wed, Jan 14, 2009 at 11:52 AM, Alan Young <ayoung at teleport.com> wrote:
>> Alex Deucher wrote:
>>> On Wed, Jan 14, 2009 at 3:15 AM, Oliver Falk <oliver at linux-kernel.at>
>>> wrote:
>>>> Matt Turner wrote:
>>>>> On Tue, Jan 13, 2009 at 3:59 AM, Oliver Falk <oliver at linux-kernel.at>
>>>>> wrote:
>>>> [ ... ]
>>>>> After working on the problem, Jay independently came to the exact
>>>>> solution Gentoo arrived at before. This, by definition, is duplication
>>>>> of effort.
>>>> Yes. That's duplication of effort. And as Jay said. Why did that happen?
>>>> Because of the lack of communication. See my other mail. A common axp
>>>> patches store would help a lot in this case.
>>> What about something like patchwork?
>>> http://patchwork.kernel.org/
>>>
>>> If everyone send patches to the list, at least they'd end up in one place.
>>>
>>> Alex
>>>
>> Is patchwork limited to vger lists (linux-alpha)?  Or can it track non-vger
>> lists?  If it could monitor the various lists (linux-alpha, redhat-axp,
>> gentoo-alpha, debian-alpha, etc.) that could help to bring patches together.
> 
> I don't know off hand, but I suspect just vger lists.  One could do
> something similar for alpha lists.

http://ozlabs.org/~jk/projects/patchwork/

We could run this somewhere for *us* (various distro alpha m/l) + axp-list.

What you think?

-of




More information about the axp-list mailing list