mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Christian <evil@g-house.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tarballs of patchsets?
Date: Mon, 24 May 2004 10:55:52 -0700	[thread overview]
Message-ID: <20040524105552.311a990b.akpm@osdl.org> (raw)
In-Reply-To: <40B21F98.1080803@g-house.de>

Christian <evil@g-house.de> wrote:
>
> i am trying to chase some bug and i know, it must be somewhere between 2.6.4 and 
>  2.6.5.

The most practical way of doing this would be to download bitkeeper and do
a binary search.


 1: Do `bk changes > foo'.

    This generates a monster changelog file which is your
    bisection-searching guide.  It has stuff like:

 ChangeSet@1.1734, 2004-05-21 22:59:48+01:00, tony@com.rmk.(none)
   [ARM PATCH] 1887/1: Update OMAP low level debug functions again
   
   Patch from Tony Lindgren
   
   This patch makes the low level debug functions work when support is
   compiled in for multiple OMAPs. The patch also removes now unnecessary
   include, incorrect comment, and SERIAL_REG_SHIFT ifdefs.


 2: Do

 	bl clone -ql -r1.1734 ref-repo test-repo

    and you have a tree up to and including 1.1734.

 3: cd test-repo ; bk -r get

 4: build, test, choose new revision, goto step 1.


It's probably possible to do the same with the CVS tree - I haven't tried.

  parent reply	other threads:[~2004-05-24 17:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-24 16:15 Christian
2004-05-24 16:33 ` Christian
2004-05-24 17:55 ` Andrew Morton [this message]
2004-05-24 22:02   ` Christian
2004-05-25 16:02   ` Andy Isaacson

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=20040524105552.311a990b.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=evil@g-house.de \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®