On Wed, Mar 07, 2007, Marcel Siegert wrote: > > what i wanted to point out is, that, in fact as a result of mercurial > installation, > > we have today 07.03.2007 11:56 including the master tree 70! repositories, > and no-one really is able to oversee what! is fixed and being in progress > where.
Well, the user repositories are just branches of the main v4l-dvb repository. I see no fundamental difference between using mercurial repositories, git topic branches or svn branches to structure development. It's just that mercurial makes them easily visible. Which I think is good. That the number is that high is not mercurial's fault. > <example> > what do i need by now, to get a dvb-s2 card running _or_ to have a > dvb-s2 repo, where > i could start developing a driver for a dvb-s2 frontend? > > which trees must i pull and merge together? > > and which one contains all fixes that have been meanwhile applied to > mainline? > > and at least - which ones, that i may merge and use, will be later on > accepted by mainline? > > the better concept _ or_ the one most people used to build their first > drivers on? > > </example> > > for me personal, it is annoying to have no central development model, where i > may rely on. I think the problem with linuxtv.org is not the SCM tool. http://linuxtv.org/hg/ : - almost no one bothers to set a useful description and goes with the default "blabla development repository" - the last change date indicates than may branches are either old cruft which someone didn't bother to remove, or someone lost interest to finish the work and get it in a state where it can be merged into mainline This is not to blame people, all I want to say that the same could happen with cvs branches, svn branches etc. Also, if someone publishes their changes, I would expect them to send a descriptive "please review, comment and test" email to one of the mailing lists. Or write something in the Wiki. The repository itself doesn't carry this meta information, but again that's the same with any SCM tool. Johannes _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
