From: Danny ter Haar <dth@dth.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: problems showing up as XFS problems on kernels after 2.6.28-git2
Date: Fri, 9 Jan 2009 22:42:06 +0100 [thread overview]
Message-ID: <20090109214206.GA2901@dth.net> (raw)
In-Reply-To: <20090109195852.GA6362@infradead.org>
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..
lenny32:/usr/src/linux-2.6# git tag|grep 2.6.28
v2.6.28
v2.6.28-rc1
v2.6.28-rc2
v2.6.28-rc3
v2.6.28-rc4
v2.6.28-rc5
v2.6.28-rc6
v2.6.28-rc7
v2.6.28-rc8
v2.6.28-rc9
So i cannot use any "standard" GIT command to also include
linus's git tree ?! that seems odd.
He committed them somehow in git didn't he ?
I could of course compile /patch 2 kernel trees by hand
in fact i allready have:
lenny32:/usr/src# ls -l
total 16
drwxr-sr-x 2 root src 146 2009-01-09 08:29 archive
drwxr-sr-x 2 root src 4096 2009-01-08 11:33 configs
drwxr-sr-x 23 root src 4096 2009-01-08 19:56 linux-2.6
drwxr-xr-x 24 root root 4096 2009-01-08 11:53 linux-2.6.28-git2-d
drwxr-xr-x 24 root root 4096 2009-01-08 10:21 linux-2.6.28-git3-d
But i'm not familiar how to instruct git to find the differences
between the 2 source tree's and how to use git to find out was
the culprit is.
Any other suggestions ?
--
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-01-09 21:42 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 [this message]
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: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=20090109214206.GA2901@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 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.