If you would have to choose between GIT and SVN or between SVN and GIT?
-
Which one would you choose and why? - For a one man team (by now). - Mainly developing on a laptop. - Connected to a server only when at home, some of the job is done remotely. PS: I hope I have not just opened the Pandora's box... I'm a Little out in terms of what is a religious discussion nowadays... :laugh:
-
Which one would you choose and why? - For a one man team (by now). - Mainly developing on a laptop. - Connected to a server only when at home, some of the job is done remotely. PS: I hope I have not just opened the Pandora's box... I'm a Little out in terms of what is a religious discussion nowadays... :laugh:
I'm using GIT at the moment, and it seems easier than SVN did - the integration with VS isn't bad at all, and that makes a big difference: Getting started with GIT, Visual Studio, and BitBucket[^]
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
I'm using GIT at the moment, and it seems easier than SVN did - the integration with VS isn't bad at all, and that makes a big difference: Getting started with GIT, Visual Studio, and BitBucket[^]
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
Which one would you choose and why? - For a one man team (by now). - Mainly developing on a laptop. - Connected to a server only when at home, some of the job is done remotely. PS: I hope I have not just opened the Pandora's box... I'm a Little out in terms of what is a religious discussion nowadays... :laugh:
This is equivalent.
-
Which one would you choose and why? - For a one man team (by now). - Mainly developing on a laptop. - Connected to a server only when at home, some of the job is done remotely. PS: I hope I have not just opened the Pandora's box... I'm a Little out in terms of what is a religious discussion nowadays... :laugh:
I use subversion. Not the Apache product; just subversion.
I wanna be a eunuchs developer! Pass me a bread knife!
-
Which one would you choose and why? - For a one man team (by now). - Mainly developing on a laptop. - Connected to a server only when at home, some of the job is done remotely. PS: I hope I have not just opened the Pandora's box... I'm a Little out in terms of what is a religious discussion nowadays... :laugh:
SVN - any day! GIT is much harder to work with and if somebody - not necessarily yourself - doesn't know how it works, you can lose code. I've experienced that at least twice... :mad:
Anything that is unrelated to elephants is irrelephant
Anonymous
-----
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-----
I'd just like a chance to prove that money can't make me happy.
Me, all the time -
Which one would you choose and why? - For a one man team (by now). - Mainly developing on a laptop. - Connected to a server only when at home, some of the job is done remotely. PS: I hope I have not just opened the Pandora's box... I'm a Little out in terms of what is a religious discussion nowadays... :laugh:
I use SourceSafe - because I don't care if nobody else likes it.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
Which one would you choose and why? - For a one man team (by now). - Mainly developing on a laptop. - Connected to a server only when at home, some of the job is done remotely. PS: I hope I have not just opened the Pandora's box... I'm a Little out in terms of what is a religious discussion nowadays... :laugh:
if (GIT && SVN) || (SVN && GIT) has redundant boolean redundancies All humor aside - on a one man team, both Git and SVN will work fine in an offline situation. But with Git, since you have a local repo, you have the opportunity to commit (or branch/merge/whatever) code locally therefore maintaining a local history. With SVN you won't be able to commit (or branch, or merge) anything while offline. So your changes will all get dumped back into the SVN repo in one big pile of committed code (depending on how long you're offline). Of course you can pick through the files and do multiple commits, but what if BUG-2387 and BUG-1209 are both in the same file? In SVN those will appear as one commit if you did them offline. With Git, you can track them as two separate commits.
-
Which one would you choose and why? - For a one man team (by now). - Mainly developing on a laptop. - Connected to a server only when at home, some of the job is done remotely. PS: I hope I have not just opened the Pandora's box... I'm a Little out in terms of what is a religious discussion nowadays... :laugh:
Git, 100% With Git you can be disconnected, you don't need to pull before you commit, and you get the chance to commit changes locally (eg when disconnected, or for just mucking around) without needing to push your changes to the main repo. The Pull Request extension is brilliant for those times you want to review changes before integrating them into master. Even better (and the killer thing for us). If your "main" repo goes down then who cares. Every other copy of your repo has all the history so you just point to another repo as your main (origin). Git is excellent for those who need to work offline and who realise that things fail.
cheers Chris Maunder
-
if (GIT && SVN) || (SVN && GIT) has redundant boolean redundancies All humor aside - on a one man team, both Git and SVN will work fine in an offline situation. But with Git, since you have a local repo, you have the opportunity to commit (or branch/merge/whatever) code locally therefore maintaining a local history. With SVN you won't be able to commit (or branch, or merge) anything while offline. So your changes will all get dumped back into the SVN repo in one big pile of committed code (depending on how long you're offline). Of course you can pick through the files and do multiple commits, but what if BUG-2387 and BUG-1209 are both in the same file? In SVN those will appear as one commit if you did them offline. With Git, you can track them as two separate commits.
Excellent reply, very good points for the situation described. Have an upvote.
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
-
I use SourceSafe - because I don't care if nobody else likes it.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013I went of SourceSafe when it totally corrupted our repository.
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
-
Git, 100% With Git you can be disconnected, you don't need to pull before you commit, and you get the chance to commit changes locally (eg when disconnected, or for just mucking around) without needing to push your changes to the main repo. The Pull Request extension is brilliant for those times you want to review changes before integrating them into master. Even better (and the killer thing for us). If your "main" repo goes down then who cares. Every other copy of your repo has all the history so you just point to another repo as your main (origin). Git is excellent for those who need to work offline and who realise that things fail.
cheers Chris Maunder
Except: Git also has squashing. Git has utter contempt for code history.
-
Which one would you choose and why? - For a one man team (by now). - Mainly developing on a laptop. - Connected to a server only when at home, some of the job is done remotely. PS: I hope I have not just opened the Pandora's box... I'm a Little out in terms of what is a religious discussion nowadays... :laugh:
Mercurial or Fossil. For Mercurial, better windows GUIs, you won't have changesets disappear (I'm looking at you detached heads) and a whole bunch of other objective and totally sound reasons unrelated to me my intense personal dislike of Git :) .
