|
I have to use Sourcesafe at work (I know, but it's out of my hands), but I've started using Git for my personal stuff. I was wondering if I could use Git at work, so that I could init a Git repo in my sourcesafe checkout, do some work, make some branches in Git, and then check back into sourcesafe after merging my Git branches into master? i.e. the checkout from sourcesafe would be the Git master, and I do all my work in branches, merging back to master when I'm happy, and then checking back into sourcesafe. It doesn't sound all that unreasonable to me, assuming I setup my .gitignore file to ignore the relevant Sourcesafe files. We're moving from Sourcesafe to Clearcase soon too  If only I could convince them to buy into Git and get Github:FI
|
#
¿
Sep 10, 2009 14:28
|
|
|
|
| # ¿ Apr 29, 2024 14:55 |
|
|
wwb posted:I think the bigger problem you'll have to deal with, vis-a-vis sourcesafe, is the whole making files readonly/locking stuff nightmare. The Sourcesafe integration with Visual Studio handles all that at the moment (when you edit the file, it checks it out and makes it writeable, vice-versa on check-in), although as you say, it is a concern of mine that once I break that link, things could go a little haywire. I'm not sure if Visual Studio will make a file writeable that it doesn't think is under version control.
|
|
#
¿
Sep 12, 2009 17:05
|
|