From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 27 02:41:46 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 18C5E16A4CE for ; Sun, 27 Mar 2005 02:41:46 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB12B43D46 for ; Sun, 27 Mar 2005 02:41:45 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 71so41170wra for ; Sat, 26 Mar 2005 18:41:45 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=tnOHuiHGIPzk45QWrEZ4gNACTkm7g9oTwkGiJKedSdDb2diNbDcn5eGF3ME7TGvAqKwJwfLqQpv+0wOaCD2ApbKfjn/VktHPzSnL04DEXwWRegaUAvTXRdlQS7y9SNkyaocjQ0UsxZkYRlsI5w29Kw2yGfJVQ3wS4BkdUwp948g= Received: by 10.54.33.61 with SMTP id g61mr320157wrg; Sat, 26 Mar 2005 18:41:45 -0800 (PST) Received: by 10.54.40.69 with HTTP; Sat, 26 Mar 2005 18:41:45 -0800 (PST) Message-ID: <2fd864e05032618419b6b2a5@mail.gmail.com> Date: Sat, 26 Mar 2005 18:41:45 -0800 From: Astrodog To: John Polstra In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <20050326233305.GA41648@xor.obsecurity.org> cc: amd64@freebsd.org Subject: Re: cvsup now broken for amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 02:41:46 -0000 On Sat, 26 Mar 2005 18:36:09 -0800 (PST), John Polstra wrote: > On 26-Mar-2005 Kris Kennaway wrote: > > > > This will obviously need to be fixed ASAP for the 5.4-RELEASE builds. > > I would fix it if I knew how. All I did was add a patch; I wasn't > expecting that to break anything. I didn't put in the binary-only > amd64 stuff and I don't know how to fix it. > > If push comes to shove, I'll back out my commit and leave it at > that. > > Johh What does the patch do?