Heinzi Tuberkel
Heinzi Tuberkel

Reputation: 103

Versioning system with per file history vs. commit history

I'm looking for a versioning system, that can show the version history with comments per file.

I've used SVN (not CVS as stated earlier) for a while and have some projects in git.

Both (svn and git) are "commit oriented" (I use this term for lack of a better one): when I look at the repository git shows all the commits, and when I open a commit, I see, which files and changes it contains.

I want it the other way around: I want to see all the files and folders currently in my repository and for each file I see the history of commits it went through.

For each commit I have to enter a summary comment as well as a per file comment describing the file's changes.

The reason I'm looking for this is my NAV (formerly Navision) designer's licence: I am allowed to change objects in my NAV system, but I can't export the sources. Therefore i only have several versions of compiled ".fob" files without any chance to see code changes, so I have to describe the change in a per file comment.

Upvotes: 0

Views: 237

Answers (2)

Lazy Badger
Lazy Badger

Reputation: 97285

CVS is file-oriented in terms of SCM: for a set of files you can't define single revision and get all files, corresponding to this (revision-slice) state

Use any current SCM, but commit single file at a time

Upvotes: 0

max630
max630

Reputation: 9238

I have to describe the change in a per file comment

This goal does not seem like a reason which makes git unsuitable. Basically, you only need to:

  • commit each file separately, not all of them at once
  • being able to query only commits which change the selected file. Which git is able to do, and is pretty reliable and fast about it, at least if you don't rename the file.

Also, you still can keep together different changes in same commit, if you find them logically coupled, just write there comments about both.

Upvotes: 2

Related Questions