CODEWITHSUNDEEP
gitstarteam
Finwood
Finwood

Reputation: 3981

create a commit although no files have changed

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?

Upvotes: 0

Views: 112

Answers (0)

Related Questions