Here are a few links that might be helpful to people learning git. Its culturally different than CVS; but once you learn it, there's no turning back. The ability to experiment with local branches, back up, rewrite history, and only publish the sanitized history is quite liberating.
http://tomayko.com/writings/the-thing-about-git http://progit.org/book/ http://git-scm.com/documentation http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html http://www.kernel.org/pub/software/scm/git/docs/everyday.html http://www.kernel.org/pub/software/scm/git/docs/user-manual.html
My suggestions - always have `gitk --all` loaded for the repo you're working on - update (not reload) gitk after modifying any branches or tags; this leaves the old objects displayed - `git reset --hard $OLDSHA1` can clean many messes, letting you try again. - reload gitk to hide deleted branches you're comfortable with losing - learn by playing around with local clones of a larger repository - install some of the git contribs, especially git-completion.bash and git-new-workdir
Later, Daniel
Hi Daniel,
Thanks for these links.
(Tapping my heels three times). I will get them into the website, I will get them into the website, I will get them into the website <smile>
very soon, really.
On Aug 30, 2009, at 11:35 PM, Daniel Herring wrote:
Here are a few links that might be helpful to people learning git. Its culturally different than CVS; but once you learn it, there's no turning back. The ability to experiment with local branches, back up, rewrite history, and only publish the sanitized history is quite liberating.
http://tomayko.com/writings/the-thing-about-git http://progit.org/book/ http://git-scm.com/documentation http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html http://www.kernel.org/pub/software/scm/git/docs/everyday.html http://www.kernel.org/pub/software/scm/git/docs/user-manual.html
My suggestions
- always have `gitk --all` loaded for the repo you're working on
- update (not reload) gitk after modifying any branches or tags; this leaves the old objects displayed
- `git reset --hard $OLDSHA1` can clean many messes, letting you try again.
- reload gitk to hide deleted branches you're comfortable with losing
- learn by playing around with local clones of a larger repository
- install some of the git contribs, especially git-completion.bash and git-new-workdir
Later, Daniel
asdf-devel mailing list asdf-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
-- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter
Daniel Herring wrote:
Here are a few links that might be helpful to people learning git. Its culturally different than CVS; but once you learn it, there's no turning back. The ability to experiment with local branches, back up, rewrite history, and only publish the sanitized history is quite liberating.
http://tomayko.com/writings/the-thing-about-git http://progit.org/book/ http://git-scm.com/documentation http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html http://www.kernel.org/pub/software/scm/git/docs/everyday.html http://www.kernel.org/pub/software/scm/git/docs/user-manual.html
Thank you very much for the suggestions, Daniel. For other ASDF developers who are trying to accustom themselves to Git, I would recommend the progit.org link above. It's the best "you are a user, here's what you need to know" of these.
Best, R