Asdo wrote:
Lee Howard wrote:
I've been deliberately monitoring the kernel via the git web
interfaces, and I can't yet see the patch committed that supposedly
fixed this. (Please correct me if it was actually committed.)
Somebody told it was fixed in 2.6.32. Have you checked that one?
Would you mind to explain me HOW to check such a thing via web git? I
wanted to do this in the past but I didn't know how to do it...
I'm not sure that I was doing it the *right* way, but go to:
http://git.kernel.org/
Click on "md raid development
<http://git.kernel.org/?p=linux/kernel/git/djbw/md.git;a=summary>".
Then if you look at the bottom for "master" head you'll go to this link:
http://git.kernel.org/?p=linux/kernel/git/djbw/md.git;a=shortlog;h=refs/heads/master
Then click on "tree" (
http://git.kernel.org/?p=linux/kernel/git/djbw/md.git;a=tree;h=refs/heads/master;hb=refs/heads/master
) to browse the repository tree. Dig a little further, and go to
drivers/md and you can see the change history in the various files to
see if a patch has been applied.
Maybe that's the wrong way to do it, but that's how I was looking.
Thanks,
Lee.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
