From: Danny ter Haar <dth@dth.net>
To: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: problems showing up as XFS problems on kernels after 2.6.28-git2
Date: Fri, 9 Jan 2009 07:10:44 +0100 [thread overview]
Message-ID: <20090109061043.GA31450@dth.net> (raw)
In-Reply-To: <20090109020800.GO9448@disturbed>
Quoting Dave Chinner (david@fromorbit.com):
> > Do you want me to figure out what patch from git2->git3 is the cullprit ?
> > I'll have to compile/reboot for a while.
> If you can do that, it would be *greatly* appreciated.
Need a little bit of help here.
(i'm a hardware guy with just the bare essential software knowhow)
I found
http://www.reactivated.net/weblog/archives/2006/01/using-git-bisect-to-find-buggy-kernel-patches/
(used that one before)
but it doesn't seem to know the "-gitXX" kernel trees.
Q:
how do i get a list of available kernel versions (including -gitXX branches)
My intention is to say something like:
# git bisect bad v2.6.28-git3
# git bisect good v2.6.28-git2
and take it from there.
I've been googling now for nearly 2hours..
Any help appreciated
Danny
--
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-01-09 6:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090107165218.GA11132@dth.net>
2009-01-07 18:02 ` problems showing up as XFS problems on kernels after 2.6.28-git2 Christoph Hellwig
2009-01-07 18:24 ` Danny ter Haar
2009-01-07 18:31 ` Christoph Hellwig
2009-01-07 18:44 ` Danny ter Haar
2009-01-07 18:52 ` Christoph Hellwig
2009-01-07 22:09 ` Danny ter Haar
2009-01-08 0:38 ` Danny ter Haar
2009-01-07 18:56 ` Christoph Hellwig
2009-01-07 19:01 ` Danny ter Haar
2009-01-08 21:56 ` Danny ter Haar
2009-01-09 0:46 ` Dave Chinner
2009-01-09 1:26 ` Danny ter Haar
2009-01-09 2:08 ` Dave Chinner
2009-01-09 6:10 ` Danny ter Haar [this message]
2009-01-09 19:44 ` Christoph Hellwig
2009-01-09 19:51 ` Danny ter Haar
2009-01-09 19:58 ` Christoph Hellwig
2009-01-09 21:42 ` Danny ter Haar
2009-01-09 22:01 ` Christoph Hellwig
2009-01-09 22:23 ` Danny ter Haar
2009-01-13 20:04 ` Danny ter Haar
2009-01-16 20:43 ` Danny ter Haar
2009-01-17 7:38 ` Dave Chinner
2009-01-17 23:25 ` Danny ter Haar
2009-01-18 2:50 ` Danny ter Haar
2009-01-19 3:17 ` Dave Chinner
2009-01-14 19:44 ` Tino Keitel
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=20090109061043.GA31450@dth.net \
--to=dth@dth.net \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.com \
/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