Add explanation of git's name#1092
Conversation
🆗 Pre-flight checks passed 😃This pull request has been checked and contains no modified workflow files, spoofing, or invalid commits. It should be safe to Approve and Run the workflows that need maintainer approval. |
erinmgraham
left a comment
There was a problem hiding this comment.
Hi Christopher, thank you for the PR! I like how you've kept most of the naming details in the README — that works well. I’m thinking we should briefly mention why Git was created and include one of Torvalds’ definitions to address the concerns raised in issue #809. For example, "Git was created by Linus Torvalds in 2005 as an open source alternative to BitKeeper, one of the first distributed version control systems, to track changes in the Linux kernel. Torvalds provided several explanations of the name, of varying degrees of politeness, which are enumerated in the
project's README, including “Global Information Tracker” for when you're in a good mood." What do you think?
I also note @martinosorb self-assigned this issue and may have other comments.
Incorporate suggestions of erinmgraham in comment to my pull request
|
@erinmgraham thanks for the very kind and thoughtful response. I have incorporated these suggestions into an additional commit. |
|
Thanks Christopher! |
Auto-generated via `{sandpaper}`
Source : 589bcba
Branch : md-outputs
Author : GitHub Actions <actions@github.com>
Time : 2025-07-31 03:12:45 +0000
Message : markdown source builds
Auto-generated via `{sandpaper}`
Source : fccca90
Branch : main
Author : erinmgraham <erin.graham@jcu.edu.au>
Time : 2025-07-31 03:12:09 +0000
Message : Merge pull request #1092 from christopherphan/name-explain
Add explanation of git's name
Auto-generated via `{sandpaper}`
Source : 589bcba
Branch : md-outputs
Author : GitHub Actions <actions@github.com>
Time : 2025-07-31 03:12:45 +0000
Message : markdown source builds
Auto-generated via `{sandpaper}`
Source : fccca90
Branch : main
Author : erinmgraham <erin.graham@jcu.edu.au>
Time : 2025-07-31 03:12:09 +0000
Message : Merge pull request #1092 from christopherphan/name-explain
Add explanation of git's name
Auto-generated via `{sandpaper}`
Source : 589bcba
Branch : md-outputs
Author : GitHub Actions <actions@github.com>
Time : 2025-07-31 03:12:45 +0000
Message : markdown source builds
Auto-generated via `{sandpaper}`
Source : fccca90
Branch : main
Author : erinmgraham <erin.graham@jcu.edu.au>
Time : 2025-07-31 03:12:09 +0000
Message : Merge pull request #1092 from christopherphan/name-explain
Add explanation of git's name
Auto-generated via `{sandpaper}`
Source : 589bcba
Branch : md-outputs
Author : GitHub Actions <actions@github.com>
Time : 2025-07-31 03:12:45 +0000
Message : markdown source builds
Auto-generated via `{sandpaper}`
Source : fccca90
Branch : main
Author : erinmgraham <erin.graham@jcu.edu.au>
Time : 2025-07-31 03:12:09 +0000
Message : Merge pull request #1092 from christopherphan/name-explain
Add explanation of git's name
Auto-generated via `{sandpaper}`
Source : 589bcba
Branch : md-outputs
Author : GitHub Actions <actions@github.com>
Time : 2025-07-31 03:12:45 +0000
Message : markdown source builds
Auto-generated via `{sandpaper}`
Source : fccca90
Branch : main
Author : erinmgraham <erin.graham@jcu.edu.au>
Time : 2025-07-31 03:12:09 +0000
Message : Merge pull request #1092 from christopherphan/name-explain
Add explanation of git's name
If this pull request addresses an open issue on the repository, please add 'Closes #NN' below, where NN is the issue number.
Closes #890
Please briefly summarise the changes made in the pull request, and the reason(s) for making these changes.
Add a short paragraph to "The long history of version control systems" callout in
01-basicsthat discusses the name of git, pointing the reader to the git project's README for information.If any relevant discussions have taken place elsewhere, please provide links to these.
Details
For more guidance on how to contribute changes to a Carpentries project, please review the Contributing Guide and Code of Conduct.
Please keep in mind that lesson Maintainers are volunteers and it may be some time before they can respond to your contribution. Although not all contributions can be incorporated into the lesson materials, we appreciate your time and effort to improve the curriculum. If you have any questions about the lesson maintenance process or would like to volunteer your time as a contribution reviewer, please contact The Carpentries Team at team@carpentries.org.