Hi, Rules can be written on the website where info on SVN access is described. But, I think that a good setup of the SVN database is required. Nobody commented the proposal I've made?
Seb. Selon Jack Carroll <[EMAIL PROTECTED]>: > On Sun, Mar 05, 2006 at 07:59:01AM +0100, Attila Kinali wrote: > > On Sat, 4 Mar 2006 11:35:44 -0500 > > Jack Carroll <[EMAIL PROTECTED]> wrote: > > > > > If someone can figure out the appropriate logic and write rules for > > > use of the tree, OGP will have made its contribution to the advancement > of > > > the engineering services profession. > > > > No need to. svn, even cvs can do that already: It's called > branching/tagging. > > I'm really surprised how little about software development > > tools is known in the EE community. And that although > > modern chip design doesn't differ much from software design > > in the used techniques. > > > I understand that svn can do that already. All that's needed is a > little written policy to tell people what branches are set up, and where to > put the files that make up a self-consistent set. > _______________________________________________ > Open-graphics mailing list > [email protected] > http://lists.duskglow.com/mailman/listinfo/open-graphics > List service provided by Duskglow Consulting, LLC (www.duskglow.com) > --Sébastien http://tetsuo3.free.fr _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
