All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Nyberg <alexn@telia.com>
To: Chuck Ebbert <76306.1226@compuserve.com>,
	Linus Torvalds <torvalds@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Making it easier to find which change introduced a bug
Date: Sat, 30 Jul 2005 14:20:07 +0200	[thread overview]
Message-ID: <20050730122007.GA8364@localhost.localdomain> (raw)
In-Reply-To: <200507300442_MC3-1-A5F6-A039@compuserve.com>

> 
> > We need a super-easy way for people to do bisection searching.
> 
>  First step would be to make interdiffs available as quilt patchsets.
> 
>  If we had this for e.g. 2.6.13-rc3 -> rc4 it would make tracking down
> those new bugs much easier.
> 
> (Yes I know git does bisection but Andrew said it should be easy.)
> __

Yeah I agree, it would be extremely useful and simplify for people
who don't have git installed.

Linus, do you think we could have something like
patch-2.6.13-rc4-incremental-broken-out.tar.bz2 that could like Andrew's
be placed into patches/ in a tree?

So for example, have a tree with 2.6.13-rc3, download
patch-2.6.13-rc4-incremental-broken-out.tar.bz2, place it in patches/ and 
be able to do quilt push / quilt pop easily.

As it stands today it's easier for us who don't know git to just find
out in which mainline kernel it works and which -mm it doesn't work in,
get the broken-out and start push/pop. And I know I'm not the only one
who has noticed this.

Thanks
Alexander

  reply	other threads:[~2005-07-30 12:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-30  8:39 Making it easier to find which change introduced a bug Chuck Ebbert
2005-07-30 12:20 ` Alexander Nyberg [this message]
2005-07-30 17:08   ` Linus Torvalds
2005-07-31  1:04     ` [PATCH] " Junio C Hamano

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=20050730122007.GA8364@localhost.localdomain \
    --to=alexn@telia.com \
    --cc=76306.1226@compuserve.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.