drm/radeon/kms: request for rebasing

2010-02-25 Thread Rafał Miłecki
Dave, we have some commits in drm-linus that are not present in
drm-radeon-testing. Maybe this is the case with other active branches
as well, don't know.

Could you rebase branches to be more clear, please? Maybe rebasing
agains .33 even?

-- 
Rafał

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: drm/radeon/kms: request for rebasing

2010-02-25 Thread Michel Dänzer
On Thu, 2010-02-25 at 10:42 +0100, Rafał Miłecki wrote: 
 Dave, we have some commits in drm-linus that are not present in
 drm-radeon-testing. Maybe this is the case with other active branches
 as well, don't know.
 
 Could you rebase branches to be more clear, please? Maybe rebasing
 agains .33 even?

I think it's great to keep branches based on the last release as long as
possible. It allows testing DRM changes easily without pulling in random
other changes.


-- 
Earthling Michel Dänzer   |http://www.vmware.com
Libre software enthusiast |  Debian, X and DRI developer

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: drm/radeon/kms: request for rebasing

2010-02-25 Thread Rafał Miłecki
W dniu 25 lutego 2010 10:46 użytkownik Michel Dänzer
mic...@daenzer.net napisał:
 On Thu, 2010-02-25 at 10:42 +0100, Rafał Miłecki wrote:
 Dave, we have some commits in drm-linus that are not present in
 drm-radeon-testing. Maybe this is the case with other active branches
 as well, don't know.

 Could you rebase branches to be more clear, please? Maybe rebasing
 agains .33 even?

 I think it's great to keep branches based on the last release as long as
 possible. It allows testing DRM changes easily without pulling in random
 other changes.

OK, I don't insist on 2.6.33. But that should not be the case when we
have few patches commited to drm-linus and few to drm-radeon-testing.
It makes some work impossible.

-- 
Rafał

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel