Change license and update leftovers #3
No reviewers
Labels
No labels
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/tzhash#3
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/license"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@ -0,0 +78,4 @@
```
```
$ git commit -sam '[#123] Add some feature'
This repo historically does not add issue numbers. Ironically, this PR too. Do we want to start?
I would stay with the old approach given the amount of changes we have here.
RLY? 😄
TMPDI
?Why backtick and not
$()
?shellcheck
usually complains.@ -0,0 +78,4 @@
```
```
$ git commit -sam '[#123] Add some feature'
I propose to use a common style across all repositories here.
Of course! =)
Agree. A blast from the past =)
@ -0,0 +78,4 @@
```
```
$ git commit -sam '[#123] Add some feature'
And I hope we could have more changes coming.
@ -0,0 +78,4 @@
```
```
$ git commit -sam '[#123] Add some feature'
Then again, what about this PR?
@ -0,0 +78,4 @@
```
```
$ git commit -sam '[#123] Add some feature'
Added proper references in commit summary. I promise to split similar bulk changes in to several logically smaller PRs next time =)