Matthias Hopf writes:

Sorry again for the fuzz. This certainly wasn't intended.

Ok, as these git commits (at least the messages) leaked out, I should probably comment on them.

Yes, we're working on 3D support for r5xx. Unfortunately, I was sidetracked for two weeks, so the "work" that has happened there is neither breathtaking nor even worth looking at. That's why I didn't commit yet. Also, we'd like to have the history clean and understandable, and only branch/merge where this is actually useful. Most (even larger) changes can be rebased, which gives a much cleaner history.

The commits have been reverted immediately in upstream git, but be assured that they'll be pushed (unaltered, except for being rebased) after we have something to show at all (the broken commit wasn't even close to being compilable, let alone having 3D working).

My new git slogan:

Always remember: Complex tools allow for complex mistakes

I tend to keep such tasks in local git branches. I've got several local branches here where I try out different things. In fact the dri work that I once started once but got stopped also still lives in a branch. All RV620 development was also done on a branch which allowed us to collaborate on these bits. Cheers, Egbert. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org