About committing to subversion
<VasudevaService-K9y3B4ipJAZZAIG4hdpdiNBPR1lH4CV8@public.gmane.org> (Priyadarshan) Fri, 23 Apr 2004 14:44:59 -0400
| Newsgroups | gmane.org.misc.vasudeva-server.web |
|---|---|
| Message-ID | <[email protected]> |
Hi, I noticed that somebody committed to svn a directory which contains two empty .py files: http://supreme.vasudevaserver.net:1300/depot/vsa/vsa_db/ Please, do not commit unless you have a meaningful, **working** code. Do not use svn as back-up system. Do not use svn for placeholders. Please commit as often as you want, as long as you do it in logical, working evolutions in your code. This can be as frequent as twice a day, or as seldom as once a week. Of course, if you commit less than once a week, that means (to me) that the development on that code is (at least temporarily) dead (that is not a good sign.) CMS (control management system) is itself an art, so you'll have to feel it. Please *always* log a brief note saying what is significant about the commit. Finally, Marek wrote a short how to to svn. You can find it plus other material here: http://www.vasudevaservice.com/search?SearchableText=subversion Thanks priyadarshan Vasudeva server http://www.vasudevaservice.com -------------------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list <VasudevaService-K9y3B4ipJAZZAIG4hdpdiNBPR1lH4CV8@public.gmane.org>.