Skip to content

Fix #15 - Windows note for hash #41

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix #15 - Windows note for hash #41

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion 1-Repository/2-introducing-the-blob.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ Now that the basic picture has been painted, let’s get into some practical exa

```bash
$ mkdir sample; cd sample
$ echo 'Hello, world!' > greeting
$ echo Hello, world!> greeting
Copy link
Owner

@jwiegley jwiegley Aug 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
$ echo Hello, world!> greeting
$ echo Hello, world\!> greeting

I think that on some shells, having an unescaped bang like this might be interpreted as a history reference?

```

Here I’ve created a new filesystem directory named “sample” which contains a file whose contents are prosaically predictable. I haven’t even created a repository yet, but already I can start using some of Git’s commands to understand what it’s going to do. First of all, I’d like to know which hash id Git is going to store my greeting text under:
Expand All @@ -14,6 +14,8 @@ $ git hash-object greeting
af5626b4a114abcb82d63db7c8082c3c4756e51b
```

NOTE this hash is for a file with LF new line endings. For Windows users that have `core.autocrlf` with a different value than `true`, this can generate a different hash.

If you run this command on your system, you’ll get the same hash id. Even though we’re creating two different repositories (possibly a world apart, even) our greeting blob in those two repositories will have the same hash id. I could even pull commits from your repository into mine, and Git would realize that we’re tracking the same content — and so would only store one copy of it! Pretty cool.
The next step is to initialize a new repository and commit the file into it. I’m going to do this all in one step right now, but then come back and do it again in stages so you can see what’s going on underneath:

Expand Down