There's no reason that KRL code cannot be maintained on Git. I've done it in the past. The vast majority of program and configuration files on a KRC are in ASCII text of some kind (the only exceptions I can think of offhand being RSI and FTC programs). You can keep the non-ASCII files in Git as well, you just won't be able to use the Diff tools on them.
What directories you want to keep in Git will depend on what you anticipate changing. Usually, end-user program code is contained in /R1/Program/, but can also be located in almost anywhere in /R1/, especially since you can create your own custom directories under that directory. Not to mention, end-user code may be include changes made to pre-installed KUKA modules like $CONFIG.DAT and SPS.SUB.
Just the C:/KRC directory should be enough. Honestly, just C:/KRC/R1 would probably do, since the files outside of /R1 are going to change pretty rarely.
C:\KRC contains way to many things
try
C:\KRC\ROBOTER\KRC
or
C:\KRC\ROBOTER\KRC\R1
...Derp. Yes, Panic is correct. I completely left out the C:/KRC/ROBOTER/ part.
i knew what you meant... 
do I have to make a git repository (.git) in WVS repository folder or somehow directly in kuka C diskdrive?
Hi,
Did you get any answer ?
What do you do so far with Git & Kuka ?
Regards
