]

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.)

(whops I forgot to cc the list... here it is)

Quoted 3 lines · Lee Howard

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?

Quoted 9 lines · On Wednesday October 21, [email protected] wrote:

(whops I forgot to cc the list... here it is)

Quoted 2 lines · Lee Howard

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?

As 2.6.32 doesn't exist yet, that should be "will be fixed".

If the problem if what I think it is, then it should be fixed by
http://neil.brown.name/git?p=md;a=commitdiff;h=1d9d52416c0445019ccc1f0fddb9a227456eb61b

which I have not yet sent to Linus.

Quoted 1 line · Lee Howard

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.