rpms/cvsup/devel cvsup-ppc.patch, NONE, 1.1 ezm3-1.2-PPC-setjmp-bootstrap.patch, NONE, 1.1 ezm3-1.2-PPC-setjmp.patch, NONE, 1.1 ezm3-1.2-ppc-jmpbufsize.patch, NONE, 1.1 .cvsignore, 1.2, 1.3 cvsup.spec, 1.5, 1.6 sources, 1.2, 1.3
David Woodhouse
dwmw2 at infradead.org
Sun Feb 13 12:22:10 UTC 2005
- Previous message (by thread): rpms/cvsup/devel cvsup-ppc.patch, NONE, 1.1 ezm3-1.2-PPC-setjmp-bootstrap.patch, NONE, 1.1 ezm3-1.2-PPC-setjmp.patch, NONE, 1.1 ezm3-1.2-ppc-jmpbufsize.patch, NONE, 1.1 .cvsignore, 1.2, 1.3 cvsup.spec, 1.5, 1.6 sources, 1.2, 1.3
- Next message (by thread): rpms/cvsup/devel cvsup-ppc.patch, NONE, 1.1 ezm3-1.2-PPC-setjmp-bootstrap.patch, NONE, 1.1 ezm3-1.2-PPC-setjmp.patch, NONE, 1.1 ezm3-1.2-ppc-jmpbufsize.patch, NONE, 1.1 .cvsignore, 1.2, 1.3 cvsup.spec, 1.5, 1.6 sources, 1.2, 1.3
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
On Sun, 2005-02-13 at 13:21 +0100, Thorsten Leemhuis wrote:
>Any specific reason why you exclude x86_64 again?
>
>Yes, i know that i does not build ATM -- I'm looking into it...
Purely an accident; sorry. For obvious reasons I was doing the cvsup
stuff on a slightly beefier machine (nice dual G5 at 2GHz) instead of the
G4 machine I'm using for the rest of the extras builds -- when I copied
the cvsup.spec back and committed I didn't realise it'd been modified in
the meantime. Want me to put it back?
--
dwmw2
- Previous message (by thread): rpms/cvsup/devel cvsup-ppc.patch, NONE, 1.1 ezm3-1.2-PPC-setjmp-bootstrap.patch, NONE, 1.1 ezm3-1.2-PPC-setjmp.patch, NONE, 1.1 ezm3-1.2-ppc-jmpbufsize.patch, NONE, 1.1 .cvsignore, 1.2, 1.3 cvsup.spec, 1.5, 1.6 sources, 1.2, 1.3
- Next message (by thread): rpms/cvsup/devel cvsup-ppc.patch, NONE, 1.1 ezm3-1.2-PPC-setjmp-bootstrap.patch, NONE, 1.1 ezm3-1.2-PPC-setjmp.patch, NONE, 1.1 ezm3-1.2-ppc-jmpbufsize.patch, NONE, 1.1 .cvsignore, 1.2, 1.3 cvsup.spec, 1.5, 1.6 sources, 1.2, 1.3
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the fedora-extras-commits
mailing list