Re: [usbip-devel] Any development against staging driver in linux mainline
Status: Alpha
Brought to you by:
hirofuchi
From: Takahiro H. <hir...@us...> - 2010-02-08 15:36:38
|
Hi, I have the same feeling. I wonder there are other open source projects which are in the same situation like us. It would be nicer if we find a good solution among them. Takahiro (2010/02/08 7:43), Brian G. Merrell wrote: > Sorry for arriving late to the discussion... > > On Sun, Feb 07, 2010 at 02:02:31PM +0100, Fritz Elfert wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> 2 weeks ago, I committed several patches here in SVN. Just do an svn log >> and you'll see. AFAIK, Brian G. Merrell is the guy who pushes them >> upstrem to Greg. From my personal point of view, I'd like to keep the SF >> SVN up-to-date (probably backporting some staging stuff). >> Reason: >> Like myself, there are shurely people out there who cannot use the >> latest kernel for various reasons (company upgrade policy, etc..) but >> still like to use USB/IP. >> >> @Brian: >> Have you picked up my patches already? > > No, I haven't. In fact, as Takahiro pointed out, there hadn't been > any real changes to the SourceForge SVN code since I did the initial > work (mostly cosmetic) to get the code into the staging tree. That > means that all of those changes never made it back to the > SourceForge SVN code, so there will be some disparity. > > Personally, I was only planning on helping to maintain the staging > tree code, and not make any more updates to the SourceForge SVN > code. However, it sounds like this does not really work for Fritz, > which is understandable. > > The difficulty I see is that now that the code is in the staging tree, > most people are going to be working on the code there, and not sending > their patches to us to apply to the SourceForge SVN repo. However, if > Fritz is working on the SourceForge SVN code, then we would also need > to make sure that those changes make it into the kernel. To me, it > makes more sense direct everyone (including ourselves) to the develop > against the staging tree code, and ask everyone to make changes there > (which has already been happening anyway), and then pull in changes > from the staging tree to the SourceForge repo on a regular basis. > This would also have the benefit of our changes having a bigger code > review audience. Since Fritz (and probably others need to compile on > older kernels), the conditionals for older kernels would remain in the > SourceForge code. > > Any thoughts? I think that if we don't use this strategy, there > will be quite painful to try and constantly reconcile differences > between SourceForge SVN changes and changes in the kernel code. > >> >> @Takahiro: >> Could you please give us admin rights. I'd really like to set up a >> proper mail notification for SVN (among other things - like enabling >> missing bug/patch/fr trackers). Furthermore: There must be some backup >> of the old wiki. (I know about that, because I'm admin of several other >> SF projects and got a notification from the SF-staff last year - they >> even offered to migrate to the new media-wiki...) >> >> Cheers >> -Fritz >> >> Himanshu Chauhan schrieb: >>> Hi, >>> >>> Is anybody developing kernel driver on the sourceforge tree? I have been working >>> on this but was sending all my patches to kernel mailing list. If anybody is >>> developing driver, wouldn't it be good that we send all our improvements to >>> kernel mailing list and get the driver from staging to mainline? >>> >>> Please let me know your comments. >>> >>> Regards >>> Himanshu >>> >>> P.S: I saw some changes in userland utils. But there was no Changelog :( >>> >>> ------------------------------------------------------------------------------ >>> The Planet: dedicated and managed hosting, cloud storage, colocation >>> Stay online with enterprise data centers and the best network in the business >>> Choose flexible plans and management services without long-term contracts >>> Personal 24x7 support from experience hosting pros just a phone call away. >>> http://p.sf.net/sfu/theplanet-com >>> _______________________________________________ >>> usbip-devel mailing list >>> usb...@li... >>> https://lists.sourceforge.net/lists/listinfo/usbip-devel >> >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.6 (MingW32) >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ >> >> iD8DBQFLbrnnboM4mAMyprARAv0AAJ95lX8tmgPPk1PgwF1ViEkU/l3q0gCfX8e0 >> xX/WUrp54i9Q9FEeFEn3y2c= >> =PYgQ >> -----END PGP SIGNATURE----- >> >> ------------------------------------------------------------------------------ >> The Planet: dedicated and managed hosting, cloud storage, colocation >> Stay online with enterprise data centers and the best network in the business >> Choose flexible plans and management services without long-term contracts >> Personal 24x7 support from experience hosting pros just a phone call away. >> http://p.sf.net/sfu/theplanet-com >> _______________________________________________ >> usbip-devel mailing list >> usb...@li... >> https://lists.sourceforge.net/lists/listinfo/usbip-devel >> >> >> ------------------------------------------------------------------------------ >> The Planet: dedicated and managed hosting, cloud storage, colocation >> Stay online with enterprise data centers and the best network in the business >> Choose flexible plans and management services without long-term contracts >> Personal 24x7 support from experience hosting pros just a phone call away. >> http://p.sf.net/sfu/theplanet-com >> >> >> _______________________________________________ >> usbip-devel mailing list >> usb...@li... >> https://lists.sourceforge.net/lists/listinfo/usbip-devel |