-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Oliver Hartkopp schrieb: > Wolfgang Grandegger wrote: >> 1. Setup can-next-2.6 to ease the maintenance of David Miller. I would >> apply *accepted* patches to this branch and tell Dave from time to >> time to pull from it. There is little benefit for normal users. > > And also for Dave as he stated here: > > http://marc.info/?l=linux-netdev&m=125207489710387&w=2 This option is not different to directly work on net-next-2.6.
>> 2. Setup a full can-2.6 git tree with *all* drivers from the SVN >> repository (excluding the old ones). That's a significant maintenance >> effort, especially to provide compatibility with older versions. > > IMO it does not make any sense to maintain backward compatible code in a brand > new kernel tree environment ... Ack. >> 3. Move the out-of-tree code from the BerliOS SVN repository to git. >> That's a valuable option, indeed. > > Ack. So we have the benefits to have a local repository were the developer can work on and creating and submitting patches becomes easier. Would be fine. > For me the current process could be: > > * For new drivers (like ems_usb.c): > > 1. Post source as a diff to net-next-2.6 on SocketCAN Core ML > 2. Make some reviews. Still needed changes: goto 1 > 3. Post source as a diff to net-next-2.6 on netdev ML > 4. Make some reviews. Still needed changes: goto 1 or 3 > 5. Acked-by: Wolfgang > 6. Done Mainlining > 7. Apply source to out-of-tree-repository > 8. Add backward compatibility stuff > 9. Done I don't like 8. This sounds simple for a simple network driver, but becomes un- maintainable for complex drivers like an USB device driver or PCMCIA board. > * For drivers that are only in the out-of-tree-repository: > > 1. Post patches as a diff to out-of-tree-repository on SocketCAN Core ML > 2. Make some reviews. Still needed changes: goto 1 > 3. Apply to the out-of-tree-repository > 4. Done > > > * For drivers that are in Mainline (and in the out-of-tree-repository): > > Post the patches/fixes for the Mainline driver as described in the process for > new drivers. > > > * To mainline drivers that are currently only in the out-of-tree-repository: > > Create a source from the out-of-tree-repository with strip-src and follow the > process for new drivers. > > > This should make it. > > And in most cases the developer can post git-patches based on net-next-2.6 > which becomes the leading development repository. Great. > It is no big difference then whether the out-of-tree-repository is a SVN or a > GIT then. I could live with both of them. It's not a difference for you, I know. ;-) But I guess persons without write access to SVN prefer a local GIT repository to better keep track of their modifications and submitting their patches. > Looks the described process sane to all of you? Let summarize: Work on already mainlined drivers or new drivers is done on net-next-2.6. Not yet mainlined drivers becomes ready for mainlining in the out-of-tree repository which we move to GIT. Ok for me. There is another option (just a thought worth). The staging-tree is indented for drivers which are not yet ready for kernel inclusion. This criteria matches for all currently not yet mainlined drivers. Why not moving them to the staging tree so we have all drivers in net-next-2.6? This would also increase the audience of kernel developers which may take look at this drivers to help us, getting them out of staging? Cheers, Sebastian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkqvJncACgkQpqRB8PJG7XwrxQCbBKnQtGSVEILvFs02YakmlfHI QiQAnijdn+OiAZ8oMcD2MOuIWgDQhWp+ =QN2B -----END PGP SIGNATURE----- -- EMS Dr. Thomas Wuensche e.K. Sonnenhang 3 85304 Ilmmuenster HRA Neuburg a.d. Donau, HR-Nr. 70.106 Phone: +49-8441-490260 Fax : +49-8441-81860 http://www.ems-wuensche.com _______________________________________________ Socketcan-core mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-core
