Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Until the Day Now Known as Before Git TFS (aka Yesterday), this was my workflow for checking in code (I work on a Mac):

* get far enough along in my code that I want to check in, launch VMWare Fusion, start Windows, login to Windows and run security updates, connect card reader, login to the VPN, oops bad password, login to the VPN again, more security updates, launch Visual Studio, connect to TFS, launch project solution file, check out my project, find the local directory on Windows where the files are stored, copy files from Mac to Windows, check in the project. Cry a bit.

And THEN: a couple hours after Git integration was announced, we moved a project I was working on over to Git on Team Foundation Service.

My new workflow:

* Make a change in the code, commit, pull, push. From INSIDE Emacs on my Mac. If you didn't know any better, you'd think I was just pushing code to GitHub.

In short, I love you.



Microsoft has a cross-platform command line TFS client (also an Eclipse plugin):

http://msdn.microsoft.com/en-us/library/gg413282.aspx

  > You can perform version control operations by using the Team Foundation 
  > Server plug-in for Eclipse. You can also use the Cross-platform Command-Line 
  > Client for Team Foundation Server to perform those tasks.
I'm not sure how Git support gets your code back into your corporate TFS server?

Edit again: did not see you using their service. It will be interesting to see how well they implemented all the ACL-type stuff, also just in general I wonder about the transport security since SSH is not supported at this time. I'd recommend against using this Visual Studio Git support to push over the internet for now!


There's no ACL for most git clients, they use standard HTTP credentials. Transport security is handled by SSL, we obviously don't expect you to pass this stuff around in plaintext!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: