Skip to contentSkip to conversation

patch-scripts, CVS, bitkeeper and kernel-sources

DISCUSSION Buttchereit, Axel (XL) 2 participants 2 messages Jan 31, 2005 – Feb 1, 2005 Framebuffer layer

lore
Share & tools
lore
#0 lore raw

Hi,

after reading "docco.txt" of "patch-scripts", browsing the mailing list archive and inspecting the "linux-fbdev" CVS repository on soureforge I'm a little confused.

Where are the sources or rather how can I access the HEAD revision (of trunk, tags and/or branches) that are required when generating a patch?

My intelfb-patch is based on 2.6.10 kernel sources that might have been patched already by gentoo (gentoo 2.6.10-r6), though I'm quite sure that "intelfb" was'nt touched. But 2.6.11-rc2-mm2 on kernel.org does obviously contain patches for "intelfb" that I wasn't aware of. (Maybe the patches that were recently posted here)

Does that mean that I have to check "kernel.org" for latest patches (change sets)? What for is this (almost empty) "linux-fbdev" CVS repository? My first thought was that this is the place where current fbdev development is taken place and that "stable releases" are transmitted to "kernel.org".

Right now I'm assuming that the truth is: I have to maintain a kernel-source-tree by my own and use the (quoting) "fragile" patch-scripts to apply bitkeeper diffs from kernel.org?

Is this all because of linux using bitkeeper and not cvs, gnu/arch (tla) or subversion?

Thanks for answering my stupid questions

--Axel

-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl

#1 lore raw
Quoted 20 lines · Axel (XL)

Hi,

after reading "docco.txt" of "patch-scripts", browsing the mailing list archive and inspecting the "linux-fbdev" CVS repository on soureforge I'm a little confused.

Where are the sources or rather how can I access the HEAD revision (of trunk, tags and/or branches) that are required when generating a patch?

My intelfb-patch is based on 2.6.10 kernel sources that might have been patched already by gentoo (gentoo 2.6.10-r6), though I'm quite sure that "intelfb" was'nt touched. But 2.6.11-rc2-mm2 on kernel.org does obviously contain patches for "intelfb" that I wasn't aware of. (Maybe the patches that were recently posted here)

Does that mean that I have to check "kernel.org" for latest patches (change sets)? What for is this (almost empty) "linux-fbdev" CVS repository? My first thought was that this is the place where current fbdev development is taken place and that "stable releases" are transmitted to "kernel.org".

Quoted 8 lines

Right now I'm assuming that the truth is: I have to maintain a kernel-source-tree by my own and use the (quoting) "fragile" patch-scripts to apply bitkeeper diffs from kernel.org?

Is this all because of linux using bitkeeper and not cvs, gnu/arch (tla) or subversion?

Thanks for answering my stupid questions

You can consider Andrew's mm tree as the development tree. (I will push next patch series soon, including yours). Note that in the -rc2 stage, only bug-fixes will be pushed to mainline. Driver addition/enhancements will be pushed to mainline in the next round, after 2.6.12 is released.

Tony

-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl