0

I am writing a porting tool to convert old Borland StarTeam repositories to git. Sometimes, though, several revisions (StarTeams counterpart to a commit in git) are identical, except for their labels.

Each revision should map to a single commit, which seems not to be possible in git, when no files differ between two adjacent commits. Currently I see two options getting this done:

  1. Write all revision labels into a single commit's message. Not the way my boss wants it to be.
  2. Create and change a dummy file, showing git something has changed. Not the nice way.

Is there any other, more elegant solution?

Finwood
  • 3,829
  • 1
  • 19
  • 36
  • 1
    `git commit --allow-empty` should work – Naman Nov 30 '15 at 08:39
  • Thanks, `--allow-empty` is exactly what I needed. – Finwood Nov 30 '15 at 09:13
  • cool, but this goes to be duplicated :) – Naman Nov 30 '15 at 09:14
  • Why would you add revision labels to a commit message? You could instead create a tag for each revision label and add all those tags to the commit. Tag is the Git equivalent for labels used by many other version control systems and probably more appropriate here than a bunch of empty commits. – sendaran Nov 30 '15 at 09:29

0 Answers0