vmmaker git migration - strange network graph

$ git fetch ben

$ git checkout -b my_vmmaker_merged_starting_point ben/vmmaker_fix_commit_dates_msgs_merge

I find it useful to review a repo's history using github's Insights > Network....

Looking at opensmalltalk's right now is a bit strange...

https://github.com/OpenSmalltalk/opensmalltalk-vm/network  

I often use the left arrow key to scroll into the past and it 

was strange that no date numbers appeared at the top for a really long time .

Looking at the feenkcom account, it was further strange that all the commits consistently spaced and to be bunched together in a single day even though they appeared to have successfully migrated their real commit date,

I'm guessing its due to the "Initial commit" of that branch being done "6 days ago" and the next child commit is several years earlier.  Probably if that initial commit was forced to a much earlier date, the vmmaker commits would become nicely spaced out in the network chart and you'd

be able to visually see which other commits each aligned with.

$ git clone feenk https://github.com/feenkcom/opensmalltalk-vm.git

$ git pull feenk

$ git checkout ab7cbba -b last_separate_vmmaker

$ git log -1

which looks right, and reviewing the first commits, the "Date:" is wrong for Ganea commit...

$ git log | tail -50 | grep -v Co-authored

After hunting around git forums a while I discovered I could do...

However that didn't fix visual issue on github.
Doing...

$ git push ben

Digging further I noticed a discrepancy in the CommitDate not matching AuthorDate...

$ git log --format=fuller | tail -55 | grep -v Co-authored

So just taking a wild stab...

$ git branch vmmaker_fix_commit_dates

$ git checkout vmmaker_fix_commit_dates

$ git log --format=fuller | tail -55 | grep -v Co-authored 

That looks better.  Lets see how it looks on github.

$ git push ben

But it seems that doesn't show up in the chart until its merged like this...

(maybe because the branch starts with an orphan commit.)

$ git merge Cog --allow-unrelated-histories

$ git push ben

One final thing.  Considering how all these VMMaker commit message are going to be intermixed with the existing history,
it may be useful to identify at a glance which ones are from VMMaker. Starting one commit back so working on the unmerged history, I did...

$ git checkout vmmaker_fix_commit_dates

$ git branch vmmaker_fix_commit_dates_msgs

$ git checkout vmmaker_fix_commit_dates_msgs

$ git filter-branch -f --msg-filter 'sed "s/^/VMMAKER: /" '

$ git log 

Looks okay

$ git push ben

$ git branch vmmaker_fix_commit_dates_msgs_merge

$ git checkout vmmaker_fix_commit_dates_msgs_merge  

Below you can see how the VMMaker commits are now spread correctly over time.  And also how the VMMaker commit could be identified.

But even consider that perhaps it would be useful for the MCZ filename to be prepended to the commit message (@peter?),
so its easier in the ancient history to exactly match up the Cog branch commits with the VMMaker commits.

So please consider deleting those crazy single-day-bunched-commits and adopting my "vmmaker_fix_commit_dates_msgs_merge" branch 

$ git remote add ben [hidden email]:bencoman/opensmalltalk-vm.git

$ git fetch ben

$ git checkout -b my_vmmaker_merged_starting_point ben/vmmaker_fix_commit_dates_msgs_merge

After that, it might even be possible to squeeze the both Cog and VMMaker branches together so there is
just one branch all the way back to ancient history, with the vmmaker commits identified to "VMMAKER" marked commit messages. 
Going forward there wont need to be that distinction.

HTH, cheers -ben