search for: elixus

To the subversion experts out there: I''d like to set up svn to maintain customizations to my base app for each client. A simple example would be to have a base CSS file and a custom one for each client. What is the best way to set up svn so I can ''co'' the trunc and then ''co'' customizations for each client on top of the base code. I''ve looked

Vladimir Prus <ghost at cs.msu.su> writes: > Why do you really need distributed development? The possible problems with > centralized development are > 1. The server might be often down. > 2. There's too much number of active branches, so nobody understand what's > going on. > 3. You can't commit while you're on a plane. Replace 3 with "You have no

http://dovecot.org/test/ Sorry for not answering any questions for past two weeks, I'll try to get around answering them in next few days. I've also been thinking about if I should switch from CVS to Darcs. It seems to be exactly the kind of reversion control tool I had wanted to use. Anyone have comments for or against it? I'd still have read-only CVS repository generated from

Chris Lattner wrote: > > Right, but you'd need HTTP/FTP server. Not a problem for *me*, but lots > > of folks are behind firewalls and can't do that. > > Sure. I can't imagine that there is a wonderful solution other than this > though. In particular, how can you do distributed development without it? > The whole idea is to reduce the need for a completely