Linux-Next discussions
 help / color / mirror / Atom feed
From: Nico -telmich- Schottelius <nico-linux-next@schottelius.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: Re: How to debug linux-next?
Date: Thu, 31 Jul 2008 16:41:11 +0200	[thread overview]
Message-ID: <20080731144111.GA4291@denkbrett.schottelius.org> (raw)
In-Reply-To: <20080731233558.ba613f33.sfr@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 2297 bytes --]

Stephen Rothwell [Thu, Jul 31, 2008 at 11:35:58PM +1000]:
> > - What's the normal way of finding out the source for a problem, if you know
> >   a good commit (9bead9ae16728973cd31d9fd60c496e0e2fabbd1) and a
> >   bad commit (dcb80fdb8cffd3fa06cd322b3e8227632ec23597)?
> 
> It is much easier to use "git bisect" within a single linux-next release
> than between releases.

Yep, that's the problem I am facing now.

> > - As far as I can see, you are doing rebase on linux-next. Why don't you
> >   continue to do git-merge?
> 
> Because some of the trees that are merged into linux-next are rebased
> fairly often as well.

Argh, such a pain. Imho it would be much nicer for tracking down
problems, if people just continue their graph, without doing rebase.

Stephen, as you've more experience with the other maintainers:
Would it not be possible to retrieve a branch from most subsystems
that is never rebased?

Imho doing rebase breaks alot of possibilities with git, as you remove
commits and break the history (which is what makes git powerful for me).

> > - And would a non-rebased tree not make life much easier for debugging
> >   purposes?
> 
> I don't know.  What it would do is produce a lot more merge conflicts as
> patches are moved around, changed, removed etc on a daily basis.

The only issue I see is with rewritten patches. Otherwise git-merge
should detect already applied patches and without git I see
git-format-patch and git-am as quite strong tools.

I must confess, that I _really_ like the idea of doing
git-fetch && git-merge linux-next, so git-bisect works
for all versions.

> > My motivation is to find out the reason why xorg crashes now together
> > with the xorg guys. But currently it seems to be impossible for me to
> > detect which commits have been between to snapshots of the master
> > branch of linux-next.
> 
> Yeah, that is a pain.  Does Linus' tree work?

Just compiling..the dual core 1.83ghz cpu is just too slow...reboot...
works. I'm writing this E-Mail running 2.6.27-rc1-denkbrett-00156-g94ad374
under xorg.

Nico

-- 
Think about Free and Open Source Software (FOSS).
http://nico.schottelius.org/documentations/foss/the-term-foss/

PGP: BFE4 C736 ABE5 406F 8F42  F7CF B8BE F92A 9885 188C

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-07-31 14:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31 12:56 xorg problems with v2.6.27-rc1-2457-gdcb80fd Nico -telmich- Schottelius
2008-07-31 13:23 ` How to debug linux-next? (was: Re: xorg problems with v2.6.27-rc1-2457-gdcb80fd) Nico -telmich- Schottelius
2008-07-31 13:35   ` Stephen Rothwell
2008-07-31 14:41     ` Nico -telmich- Schottelius [this message]
2008-07-31 15:58       ` How to debug linux-next? Takashi Iwai
2008-07-31 16:09         ` Nico -telmich- Schottelius
2008-07-31 16:36           ` Takashi Iwai
2008-07-31 16:54             ` Nico -telmich- Schottelius
2008-07-31 16:59               ` Takashi Iwai

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=20080731144111.GA4291@denkbrett.schottelius.org \
    --to=nico-linux-next@schottelius.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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