[tpm] Follow-up to Lightning Talks

[Shawn Sorichetti]

Hi Alan,

It wasn’t an empty file at the beginning it was an empty git commit. To create one issue the command:

git commit —allow-empty —message “Initial commit”

This will allow you to rebase all the way back to the beginning of the repository.

The other option, which I still haven’t got around to trying is to issue:

git rebase -i —root

This is supposed to allow rebasing of the very first commit.

~Shawn

>> On Sep 29, 2019, at 1:23 PM, "arocker at vex.net" <arocker at vex.net wrote:
> 
> There was a suggestion that when creating a new program in a Git
> repository, it's a good idea for the initial commit always to be an
> "empty" file.
> 
> If this is being done as a step in an automatic process to start from a
> generic skeleton, would it be better:
> 
> a) just to "touch" the name, then add and commit, before writing the file
> b) write the generic file, add & commit
> c) not important either way?
> _______________________________________________
> toronto-pm mailing list
> toronto-pm at pm.org
> https://mail.pm.org/mailman/listinfo/toronto-pm