14.06.2011 22:31, davidMbrooke пишет: > Hi, > > We are getting a few requests for additional kernel modules for 4.0: one > request on leaf-user for asix.ko and I also got a direct request for > r8168.ko the other day. IMHO it would be good to make those available > via version 4.0.1 and maybe later a 4.0.2 etc. > > We also have a large number of fairly major changes (including a kernel > version change) building up in Git. My expectation is those will take a > while to mature, via several Beta releases, and so aren't likely to make > it to "final" release status anytime soon. > > I therefore suggest that we call the next release of the Git HEAD > 4.1-beta1 and then also release 4.0.1 as a "branch" release containing > just *minor* enhancements and bug fixes for 4.0. > > Comments? > > davidMbrooke IMHO before tagging other versions we should make decisions on some questions on git: 1) In what way we should maintain releases - as branches, or as repositories? 1st IMHO is preferrable when there is not many different branches; 2) How about reducing directory depth? IMHO it'll be good to move buildtool and binary to the git root - separate directories for projects are meanles for git (for that purposes there are repositories)ю Ьфниу we should bove BuC4 into separete gepository (for ex., leaf/buc4 instead of leaf/leaf)? 3) Maybe somebody have other questions/propositions about git organization?
P.S. About USB NIC - maybe we should enable them all? ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel