All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Danny ter Haar <dth@dth.net>
Cc: 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 17:01:38 -0500	[thread overview]
Message-ID: <20090109220138.GA5282@infradead.org> (raw)
In-Reply-To: <20090109214206.GA2901@dth.net>

On Fri, Jan 09, 2009 at 10:42:06PM +0100, Danny ter Haar wrote:
> Quoting Christoph Hellwig (hch@infradead.org):
> > There is no specific 2.6.28-git respository, just a main linux 2.6 one:
> > 	git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> > The git bisect command make sure you will get the right revisions
> > checked out to bisect.
> 
> still not making myself clear i guess..

Or me beeing stupid, sorry :)  The -gitN thingies aren't
official tags, but unofficial snapshots done by Dave Woodhouse.

He has a mapping on
http://www.kernel.org/pub/linux/kernel/people/dwmw2/snapshot-tags/ from
these names to actual tags.  So 2.6.28-git2 would be

	3c92ec8ae91ecf59d88c798301833d7cf83f2179

and 2.6.28-git3

	6a94cb73064c952255336cc57731904174b2c58f

so use

git bisect good 3c92ec8ae91ecf59d88c798301833d7cf83f2179
git bisect bad 6a94cb73064c952255336cc57731904174b2c58f


Sorry for the confusion..

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-01-09 22:02 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07 16:52 problems showing up as XFS problems on kernels after 2.6.28-git2 dth
2009-01-07 18:02 ` 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
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 [this message]
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:42 ` Tino Keitel
2009-01-14 19:44 ` Tino Keitel
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=20090109220138.GA5282@infradead.org \
    --to=hch@infradead.org \
    --cc=dth@dth.net \
    --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 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.