darcs record, then darcs push. (same for git)
In svn however, its a simple svn commitOn the other hand you retain features like private branches, shelving etc. However, every feature is also a burden in terms of what you need to learn. If you just do the record, you'll never notice that your changes never went to the central repos.
Linus comments on svn have been around for a while, he starts out with "I hated cvs, so I hate svn". "By definition everyone who disagrees with me is stupid." I doubt he ever used it, and he also misquotes the svn slogan as "CVS done right." So well, it's a bit of a religious war being waged here. He never compares SVN and git, he always compares git with CVS, granted, in that case git shines. So does darcs, hg and so does svn. CVS dates back for like 20 years. Branching and merging in CVS is a pita, it's by far easier in SVN.
SVN works for lots of people, does some things right and maybe some things wrong. Most centralized models fail when you have people often disconnected because you can't commit on the road. They also fail often for Open Source because of required commit access - however, companies have a different stance on that. Distributed models imply that everybody has access to the full repository and everybody can clone a repo from everyone who has one. Maybe that's something that I do not want. In a distributed env, commits to a branch happen to the local repo instead of a branch on the central repo - maybe me, as the responsible person I don't want that. I want all commits to go to a central repo so I can see what happens.
Oh, and while we're at it - I'd choose darcs over git any time of the day.
cheers felix On Jul 1, 2009, at 11:00 AM, Simon Cornelius P Umacob wrote:
Well, Linus some interesting opinion on SVN: http://www.youtube.com/watch?v=4XpnKHJAok8 =) git/hg can be centralized too, if you make your workflow as such. While there is no central repo, you can agree that one of your repos be treated as the official one. All synchronization can be done between the official repo and your working copy, *in addition to being able to synchronize to other people's copies as well*. CVS/SVN also swaps patches too; isn't getting the diff of your files equivalent to getting the patches too? [ simon.cpu ] On Wed, Jul 1, 2009 at 4:47 PM, Felix Gilcher<[email protected]> wrote:I'd recommend SVN as well. Judging from my experience people that are new to version control systems have an easier time wrapping their mind around acentralized model. There's a master copy (repository) and a number ofworking copies. All synchronization happens between the repository and the wc. Decentralized version control systems have a number of copies, each onea repository at the same time. You're not synchronizing but swappingpatches. While that may or may not be an advantage for your developmentmodel, it certainly complicates things. cheers felix On Jun 30, 2009, at 11:48 PM, David Zülke wrote:Probably SVN with Versions.app as the client if the other person does nothave a strong technical background or command line ninja skills. - David On 30.06.2009, at 16:23, Michal Charemza wrote:Hi, I was wondering what would be a good version control system for an Agavi project? I do have some specific notes: - It is just a team of two (me and one other) - The other person is not very familiar with PHP (they will be handling more of the graphical design, images, CSS etc). - The other person is unfamiliar with the command line: so a way of dealing with the system in a more graphical fashion would be best - We are both Mac-based.Any suggestions / thoughts would be very welcome. I see Git is quitepopular nowadays...? Michal. _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users_______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users-- Felix Gilcher Bitextender GmbH Paul-Heyse-Str. 6 D-80336 München T: +49 89 57 08 15 16 F: +49 89 57 08 15 17 M: +49 172 840 88 28 [email protected] http://bitextender.com/ Amtsgericht München, HRB 174280 Geschäftsführer: David Zülke, Florian Clever _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users_______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
-- Felix Gilcher Bitextender GmbH Paul-Heyse-Str. 6 D-80336 München T: +49 89 57 08 15 16 F: +49 89 57 08 15 17 M: +49 172 840 88 28 [email protected] http://bitextender.com/ Amtsgericht München, HRB 174280 Geschäftsführer: David Zülke, Florian Clever
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
