-
-
Notifications
You must be signed in to change notification settings - Fork 909
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.
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
Adds a little more to the SHA1 identifier explanation #51
Conversation
@hlapp Thanks for the pull request. We try to not add much information at the novice material because there is already too much things to students learn. But since you wrote a very brief explanation I'm 👍 to merge this. |
On Fri, Feb 13, 2015 at 04:54:30AM -0800, Raniere Silva wrote:
I'm less sure ;). “will be globally unique” is too strong, since you |
So, when I taught this, I did show them the whole beast right away ( |
True. However, isn't this a detail that will be (rightfully) lost on students, and for all intents and purposes for why, where, and to whom we are teaching this, aren't these identifiers close enough to globally unique to be called that way? Linus Torvalds is quoted as saying:
|
On Fri, Feb 13, 2015 at 03:02:10PM -0800, Hilmar Lapp wrote:
Absolutely. I meant "this wording is too brief to be correct, and I agree that starting with the data model is a valid approach, and I For what it's worth, the Git user manual [2,3] also talks about |
Yes, but you have to do a commit first :) Right after the first commit, some learners are going to ask about the output of Your changes are very valuable and I see two places to include them. We can add them after the first time the full checksum shows up, i.e. after The other place to add them is the first time you need to write the commit-id at all, i.e. when Either is fine to me. I also think an entry in the glossary is pertinent. It could include not only the link, but also a couple of short sentences that help the learners to understand:
|
Yes, indeed, I meant after the first commit. Sorry if that wasn't clear. |
On Fri, Feb 13, 2015 at 04:17:36PM -0800, Ivan Gonzalez wrote:
Or you can follow the Git user manual and start with a clone 1, then
These both sound like reasonable places to me, but I'd consider moving |
I vote for:
|
I can do that but likely not before April. Sorry, been booked solid. |
No problem, we can wait. I'll merge other PRs then and you may need to rebase. Thanks a lot! El 09/03/2015, a las 11:06, Hilmar Lapp notifications@github.com escribió:
|
Redone as and superseded by #164. Closing. |
No description provided.