Town Car Version Control
joelonsoftware.com
Town Car Version Control
1–10 of 23 posts
Re: Town Car Version Control
#2This seems like a cool solution, I don't know if any of the other big providers are doing synchronized repos, do other similar solutions exist?
Re: Town Car Version Control
#3All version control systems have to support Git these days or they are headed for irrelevance.
Re: Town Car Version Control
#4It's good to see FogCreek being practical and adding in Git support, based on how strong they were pushing for Mercurial before (Joel even had an online training[0]) I wouldn't have guessed they would ever switch to Git, but as Joel said "Religious war: averted." I wish more software would mitigate these debates with solutions like this, but its often not that easy. This seems like a cool solution, I don't know if an…
There are places where this is valuable enough to be worthwhile (say.. ANSI SQL and related high-level-language database agnostic libraries). I'm not convinced source control is one of those places.
For fogcreek, they bet the farm on hg and are presumably seeing an opportunity cost to that decision that this mitigates. This makes loads of sense for them. I'm not convinced it's all that awesome for the rest of us, or for either the hg or git user bases as a whole.
Re: Town Car Version Control
#5This Kiln ad/blog post conveniently dances around how GitHub also does the same 'corporate things'. All version control systems have to support Git these days or they are headed for irrelevance.
Re: Town Car Version Control
#6Re: Town Car Version Control
#7It's good to see FogCreek being practical and adding in Git support, based on how strong they were pushing for Mercurial before (Joel even had an online training[0]) I wouldn't have guessed they would ever switch to Git, but as Joel said "Religious war: averted." I wish more software would mitigate these debates with solutions like this, but its often not that easy. This seems like a cool solution, I don't know if an…
> Plastic SCM [...] developed an importer that supports the fast-import
> format introduced by Git and widely used to migrate from other systems
Most source control systems assume a one-time import because they are so awesome there's no doubt you'll want to keep your code there forever, but the trend is to support at least Git semi-synchronously.http://codicesoftware.blogspot.com/2013/01/using-plastic-scm...
http://www.perforce.com/git-fusion
http://blogs.msdn.com/b/bharry/archive/2012/08/13/announcing...
Re: Town Car Version Control
#8This Kiln ad/blog post conveniently dances around how GitHub also does the same 'corporate things'. All version control systems have to support Git these days or they are headed for irrelevance.
Hmm, if i did say that all browsers have to run on Webkit these days or...
http://alistapart.com/article/the-vendor-prefix-predicament-...
Re: Town Car Version Control
#9It has to somewhat hurt that Microsoft just released and is rapidly improving some quite decent Git support in Visual Studio (and on the server side, Team Foundation Server).
http://www.hanselman.com/blog/GitSupportForVisualStudioGitTF...
> choose either Git or Team Foundation Version Control (TFVC) as the source provider
[edit: technically also at CodePlex]Re: Town Car Version Control
#10It has to somewhat hurt that Microsoft just released and is rapidly improving some quite decent Git support in Visual Studio (and on the server side, Team Foundation Server).
Pardon my ignorance, but Microsoft supporting Git server-side is only if they host it for you at http://tfs.visualstudio.com/ , correct? http://www.hanselman.com/blog/GitSupportForVisualStudioGitTF... > choose either Git or Team Foundation Version Control (TFVC) as the source provider [edit: technically also at CodePlex]