gnu-arch-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] Linux BKCVS to GNU Arch Script


From: Paul Mundt
Subject: Re: [Gnu-arch-users] Linux BKCVS to GNU Arch Script
Date: Mon, 28 Feb 2005 14:15:59 +0200
User-agent: Mutt/1.5.6i

On Mon, Feb 28, 2005 at 10:24:16AM +0000, Catalin Marinas wrote:
> > Lets see if 1.26789 lines up with what is in BK.. it's going to take
> > awhile to build up to these patch levels in my revlib, so I will keep you
> > posted once this finishes up.
> 
> Do a grep in {arch}/..../patch-log for this number and do a "tla
> get-changeset" on that patch number. You can look afterwards in the
> directory created, it is much faster than using the revlib (actually I
> always make sure not to use library revisions with this repository
> since it takes ages to create).
> 
Yeah, that's not a bad idea. Well, if I fetch this changeset specifically
it doesn't include any patches, only the patch-log. This would certainly
seem to be the cause of the problem. I've attached the patch-log for
this (patch-2007), let me know if you want me to tar up the changeset.

> > I started tracking at 2.6.10 (I figured I would start out with the
> > example you provided to make sure nothing out of the ordinary happened,
> > prior to trying to go back any further). So the ,bkcvs-last-rev I had
> > when starting out was 1.24782.
> 
> I think it is better to do some intermediate diffs on -rcX releases
> with the kernel.org archives to make sure there are not differences.
> 
I'll start diffing and seeing if there are other missed bits..

> Well, I meant patch-1, I realised that base-0 is the initial import
> and the file list want tell much. Patch-1 log shows the first BKCVS
> revision you used, that's what I was interested in.
> 
Attached as well..

Attachment: linux--stable--2.6--patch-1.log
Description: Text document

Attachment: linux--stable--2.6--patch-2007.log
Description: Text document

Attachment: pgpB66gKJtpB9.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]