Hi Mike. I created new module bering-uclibc4 <http://leaf.cvs.sourceforge.net/viewvc/leaf/src/bering-uclibc4/>for this branch (to leave 3.x buildenv working & unchanged - possible somebody needs tiny 2.4 kernel based distro) in /leaf/src. It looks that after module creation CVS doesn't grant rights for write access on it for me. > On Tue, 2010-04-27 at 01:04 +0300, Andrew wrote: > >> # cvs commit >> cvs commit: Examining . >> [email protected]'s password: >> ? radcoad.init >> ? buildtool.mk >> ? buildtool.cfg >> **** Access denied: Contact project administrator if you must write here. >> cvs commit: Pre-commit check failed >> cvs [commit aborted]: correct above errors first! >> >> It's my mistake (I didn't use CVS before, only have experience with >> Mercurial), or there are troubles with access lists? >> > Andrew, > The last commit I see is mine giving you write access to the > bering-uclibc directories on the 15th. Did you successfully checkout a > working copy? > > http://sourceforge.net/mailarchive/forum.php?thread_name=E1O2PuV-0006K8-3s%40sfp-cvsdas-2.v30.ch3.sourceforge.com&forum_name=leaf-cvs-commits > http://leaf.cvs.sourceforge.net/viewvc/leaf/ > > SourceForge CVS help. > http://sourceforge.net/apps/trac/sourceforge/wiki/CVS > > Note: I have svn and git enabled, and I can give you access. If > requested, I'll enable mecurial for your use. We need to move away from > cvs anyway. > >
------------------------------------------------------------------------------ _______________________________________________ leaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-devel
