I am currently using "JEDI" as a version control tool. One of Jedi's limitations is that it exclusively locks a file when a developer checks it out. In my opinion this is a complete productivity killer. I have been told that Jedi is the way to go because it was specifically designed to handle Delphi projects (for example it checks out the dfm and .pas files together and so forth).

-
I am currently using "JEDI" as a version control tool. One of Jedi's limitations is that it exclusively locks a file when a developer checks it out. In my opinion this is a complete productivity killer. I have been told that Jedi is the way to go because it was specifically designed to handle Delphi projects (for example it checks out the dfm and .pas files together and so forth).

I would like to switch to git instead. Can anyone provide me some feedback on this? In particular I would be interested in knowing how git can be used with large Delphi code bases. How difficult would it be to branch and merge?

Comments

  1. David HeffernanAugust 23, 2017 at 9:04 AM

    The IDE integrations will do that won't they? Not sure what you mean though about treating as a single entity. You mean you never change one but not the other?

    ReplyDelete
  2. Scott PinkhamAugust 23, 2017 at 9:58 AM

    David Heffernan I haven't used the IDE integrated version control - had too many problems with it in the past (older IDE's didn't work with newer versions of SVN), but maybe I should revisit it? Since the .pas is of no use without its corresponding form, I'd like the VCS to treat them as a 'bundle' since I always work on them together.

    ReplyDelete
  3. David HeffernanAugust 23, 2017 at 11:43 AM

    In reality that's not what happens. Sometimes you change one but not the other. There's really no issue here. If you ever work with a system that just treats them as distinct files you'll find it's no problem.

    ReplyDelete

Post a Comment