Thread (1 message) 1 message, 1 author, 2016-07-25

Re: [RFC] A Change to Commit IDs Too Ridiculous to Consider?

From: Junio C Hamano <hidden>
Date: 2016-07-25 17:11:27

Junio C Hamano [off-list ref] writes:
Jon Forrest [off-list ref] writes:
quoted
Sure. Take a look at the 2nd or 3rd chapter of Pro Git Reedited, 2nd
Edition (or just Pro Git 2nd Edition - it doesn't matter). You see
lots of output showing 'git commit' commands and the commit IDs that
result. I suspect you'd see the same in almost any book about Git.
I would think that the early-stage learners are better served that
it is the norm, not anything strange, that the commit object name
would be different when you do two identical sequence from scratch.
Ehh, sent without proofreading.  The above should say "... are
better served if the book taught that it is the norm, ...".
Forcing them to know GIT_*_DATE variables, just to give them an
impression as if setting of them is part of any normal workflow (or
more importantly, stable commit IDs made by different people at
different times is something expected), is doing them double
disservice, IMHO.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help