public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>, bcollins@debian.org
Subject: Re: bkcvs problems?
Date: Wed, 8 Oct 2003 08:38:32 -0700	[thread overview]
Message-ID: <20031008153832.GA9561@work.bitmover.com> (raw)
In-Reply-To: <20031007191433.GA683@elf.ucw.cz>

Fixed.  Ben, please check the SVN tree to see if it is OK.  I suspect
it is, I believe that the problem was a screwed up ssh key so the CVS
archive on kernel.bkbits.net was not getting updated.

On Tue, Oct 07, 2003 at 09:14:35PM +0200, Pavel Machek wrote:
> Hi!
> 
> According to bkbits, andi's cpufreq changes are in:
> 
> http://linus.bkbits.net:8080/linux-2.5/patch@1.1480?nav=index.html|ChangeSet@-1d|cset@1.1480
> ....
> diff -Nru a/arch/x86_64/kernel/Makefile b/arch/x86_64/kernel/Makefile
> --- a/arch/x86_64/kernel/Makefile	Fri Sep 26 06:53:37 2003
> +++ b/arch/x86_64/kernel/Makefile	Sun Oct  5 13:31:26 2003
> @@ -26,3 +26,5 @@
>  
>  bootflag-y			+= ../../i386/kernel/bootflag.o
>  cpuid-$(CONFIG_X86_CPUID)	+= ../../i386/kernel/cpuid.o
> +
> +obj-$(CONFIG_CPU_FREQ)	+=	cpufreq/
> ....
> 
> but bkcvs thinks otherwise:
> 
> head	1.26;
> access;
> symbols;
> locks; strict;
> comment	@# @;
> expand	@o@;
> 
> 
> 1.26
> date	2003.09.26.15.56.18;	author ak;	state Exp;
> branches;
> next	1.25;
> ...
> 1.26
> log
> @Another small x86-64 merge
> 
> (Logical change 1.13489)
> @
> text
> @#
> # Makefile for the linux kernel.
> #
> 
> extra-y 	:= head.o head64.o init_task.o vmlinux.lds.s
> EXTRA_AFLAGS	:= -traditional
> obj-y	:= process.o semaphore.o signal.o entry.o traps.o irq.o \
> 		ptrace.o i8259.o ioport.o ldt.o setup.o time.o sys_x86_64.o \
> 		x8664_ksyms.o i387.o syscall.o vsyscall.o \
> 		setup64.o bluesmoke.o bootflag.o e820.o reboot.o warmreboot.o
> 
> obj-$(CONFIG_MTRR)		+= ../../i386/kernel/cpu/mtrr/
> obj-$(CONFIG_ACPI)		+= acpi/
> obj-$(CONFIG_X86_MSR)		+= msr.o
> obj-$(CONFIG_X86_CPUID)		+= cpuid.o
> obj-$(CONFIG_SMP)		+= smp.o smpboot.o trampoline.o
> obj-$(CONFIG_X86_LOCAL_APIC)	+= apic.o  nmi.o
> obj-$(CONFIG_X86_IO_APIC)	+= io_apic.o mpparse.o
> obj-$(CONFIG_PM)		+= suspend.o
> obj-$(CONFIG_SOFTWARE_SUSPEND)	+= suspend_asm.o
> obj-$(CONFIG_EARLY_PRINTK)	+= early_printk.o
> obj-$(CONFIG_GART_IOMMU)	+= pci-gart.o aperture.o
> obj-$(CONFIG_DUMMY_IOMMU)	+= pci-nommu.o pci-dma.o
> 
> obj-$(CONFIG_MODULES)		+= module.o
> 
> bootflag-y			+= ../../i386/kernel/bootflag.o
> cpuid-$(CONFIG_X86_CPUID)	+= ../../i386/kernel/cpuid.o
> @
> ....
> 
> (Of course, I initally tried with simple cvs update, then I killed
> whole tree and did cvs update, but that did not help. I did bk sync
> five minutes ago, just to be sure, but it did not help).
> 
> 								Pavel
> 
> -- 
> When do you have a heart between your knees?
> [Johanka's followup: and *two* hearts?]

-- 
---
Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm

  reply	other threads:[~2003-10-08 15:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-07 19:14 bkcvs problems? Pavel Machek
2003-10-08 15:38 ` Larry McVoy [this message]
2003-10-08 15:51   ` Ben Collins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20031008153832.GA9561@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=bcollins@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox