On Tuesday 04 August 2009, Kern Sibbald said something like: > We have planned to give all developers write access to the bacula > github repository. By all developers, I mean the ones that have > write permission to the SVN.
That makes sense. > Git has many advantages over SVN that I will not go into, but it does > have at least three disadvanges: > > 1. It is far more complex than SVN Very true. With great power, comes great complexity...or something like that. :) > 3. It is *way* too easy for a developer to "rewrite" the repository > history. This is true, but I guess the rationale is you expect your "trusted" developers not to do something stupid to your master repo. > Despite the above disadvantages, I am totally convinced that there > are so many advantages of git, that it will significantly improve the > way Bacula developers work together. Certainly. I learned git for a job nearly a year ago, and now prefer it to SVN. Its zero-cost branches and merging are fantastic, even if you use a "mostly centralized" development model, as most projects seem to do. > and Source Forge only permits one git repository Ah, bummer. Thanks for the notes and explanations. j -- Joshua Kugler Part-Time System Admin/Programmer http://www.eeinternet.com PGP Key: http://pgp.mit.edu/ ID 0xDB26D7CE ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
