Goubier Thierry wrote
I didn't understand that you could, instead of the branch, use a tag or a commit ID as the version identifier
Something interesting I read recently that helped me understand git better is that a "branch" is just a pointer to a commit, just like a release tag. The history of the branch is available, not because there is a "branch object" that stores/calculates it, but because commits are linked back to their ancestors. If you arbitrarily change the #myBranch pointer to point to a different commit, you'd automatically get that commit's history. So I'm seeing that there is a tree of commits, with references to various leaves, called "tag" or "branch" or "id" depending on the use context. IIRC even when you do a rebase it doesn't change that commit (call it x), but creates a new commit x' and changes the pointer to point to it. I am a git beginner, so feel free to correct or augment the above... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Fast-way-to-load-package-form-github-tp4756579p4756686... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.