Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Development Tools Git Basics Getting Started With Git Looking Back on What We've Done

rajbee
rajbee
6,657 Points
Posted by rajbee
rajbee
6,657 Points

Your own number instead of hashes for commit identifiers ?

You mentioned that hashes are way better than numbers assigned to a commit by developers/human because developers could assign conflicting numbers etc.

Git is a DVCS or distributed VCS. Each developer has his/her own copy of the repo. So, I understand that each local copy of git repo generates a hash and assigns it to a commit. Is it possible that another developers repo generates the same hash, thereby creating a conflict when both their repo codes are merged ?

1 Answer

Michael Hall
PLUS
Michael Hall
Courses Plus Student 30,909 Points
Michael Hall
Michael Hall
Courses Plus Student 30,909 Points

here is what one of my commits looks like: commit bcad180b675bdebde9cee987e76e0c17e8463abc, as you can see, the odds of another developer pushing with that exact same commit is pretty unlikely, although, I guess it's possible.