I'd put gitk at the top of the list for newbies. It really, really, helps.
If you're confused about what git is doing at any time, please understand that as long as you are working on clean (everything committed) trees, the reflog will always get you back to some prior state, even if you thought you lost stuff. Sitaram On Tue, Aug 11, 2009 at 10:14 PM, gberz3<[email protected]> wrote: > > Hi All, > > Doing my best to not go ballistic here. =P Ok, I followed the > (admittedly conflicting) instruction on reverting changes in a git > repository. I used the following: > > git reset --hard HEAD^ > > Basically, I have two branches: "master" and "devbranch". I was about > 4 commits up on "devbranch" when I decided that I didn't want my > existing changes since the most recent commit. In an effort to go > back to the most recent commit on "devbranch" I performed the previous > command. Well, it took me back to the last commit that matched up > with "master". Needless to say, I lost a *TON* of work. > > I'll be the first to admit that I'm no source-control guru, but items > like this should be documented (and probably implemented) in more > straightforward, intuitive terminology. Can someone direct me (at > least for the time being) to the "simpleton" version of GIT > documentation? > > Best. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/github?hl=en -~----------~----~----~----~------~----~------~--~---
