From owner-freebsd-current@FreeBSD.ORG Mon Dec 28 17:38:01 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ECE3C1065670; Mon, 28 Dec 2009 17:38:01 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mx1.freebsd.org (Postfix) with ESMTP id 57FF98FC19; Mon, 28 Dec 2009 17:38:01 +0000 (UTC) Received: by ewy26 with SMTP id 26so7560853ewy.3 for ; Mon, 28 Dec 2009 09:37:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=pWgIgjM8iSwmmzVWzTdBCU0Uu8nD3SW/pEYdsN1i0mI=; b=fmPzATJwSzMXP4UBvepChMXXa++QeKASTuO92RcZTFhP3oaCH+OeZ7lh8pyA0vJ6rz lRctXWdp9wnUaZ2t1xA/Pfl6GxsfTvjgUOUeY+Vx6nf1Mk5wm//7SIfnpMrxzDnVuvur /BERhlg236FYMk5uMC9A/7ryqL3Vj2fbNsavE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Rcmf8NPD8urecjmVpCsGEgA35Ze6elNK0qfVUqkRDK4cnY2qP+6MNlI2mdonK7BEal niarK23E+F5xX/xJccAz0VtrIgXjdXL/Tls4dgEYTXoW0893Bmwg1DLjyLrxb6dPCq33 oG/5FzLmU9KSnKdiPC2XbMA/+PjZFWMG4hBz4= MIME-Version: 1.0 Received: by 10.216.91.15 with SMTP id g15mr6259773wef.24.1262021872209; Mon, 28 Dec 2009 09:37:52 -0800 (PST) In-Reply-To: <86zl53105u.fsf@ds4.des.no> References: <20091222174248.GA61700@mech-cluster241.men.bris.ac.uk> <86ws072she.fsf@ds4.des.no> <200912281058.40733.jhb@freebsd.org> <86zl53105u.fsf@ds4.des.no> Date: Mon, 28 Dec 2009 12:37:52 -0500 Message-ID: From: "b. f." To: =?ISO-8859-1?Q?Dag=2DErling_Sm=F8rgrav?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, Anton Shterenlikht Subject: Re: still trouble with pci.c on i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Dec 2009 17:38:02 -0000 I think John is referring to my first reply to Anton, early in the thread, in which I said that I thought it would be easier for Anton to get help for problems with -CURRENT by using svn revision numbers, because most base system developers were using that VCS. Apparently, John at least is not using svn exclusively, and is willing to look up cvs revision numbers. b. On 12/28/09, Dag-Erling Sm=F8rgrav wrote: > John Baldwin writes: >> Dag-Erling Sm=F8rgrav writes: >> > This discussion is pointless if your source tree is not a Subversion >> > working copy. >> That's not true. I still use cvsweb quite often as one can more easily >> see >> what has been MFC'd that way rather than with the svn equivalent. And i= t >> is >> easy to use cvsweb to find a particular CVS revision and map it to an SV= N >> revision. > > The discussion was about using Subversion to woll back commits in what > was in all probability either a cvsup checkout or a CVS working copy. > > DES > -- > Dag-Erling Sm=F8rgrav - des@des.no >