Subject: DocOz Episode: Firm Tummy - 7 Days

From: DocOz Exclusive Edition <[email-masked]>
Date: Tue, 19 Aug 2014 13:07:17 -0700

What's Buzzing on Daytime TV:

They Way to Stop Absorbing Carbs -

Read it - See it - Believe it!

You can literally eat whatever you want, and not deal with the consequences. 
In 60 seconds you will have the metabolism of a skinny person. 

See DocOz Clip: http://www.rectgas.com/carb/blocker/approved.index

----------------------
View Reviews: August 1, 2014
I started using this after watching Dr.Oz Show and found out that I
can block carb absorption which is what I am looking for. 
Exercising is important but limiting carb is very tough for me.
Im down 40 lbs and happier than ever!

-
-
-
To change notification settings - visit here- http://www.rectgas.com/94jj/jjg55.11wsxc or write to Daily Updated Alerts
9306 BOVA CT
Louisville, KY 40291

-
-

Doesn't work with OS x. - I get "ambiguous argument 'HEAD^' ... Unknow revision or path not in the working tree". Using he tilde version makes no difference. But git log and git status both appear to show there is a  are you trying to undo? The first commit? If you're trying to undo the first commit and go back to zero commits, the easiest thing would probably be to delete the repository (but not your code) and , I think that might be the problem. In this case, I committed something I thought was small - and when I tried to Push, I found it was 400 MB of data (!) (a deep nested Resources folder containing video and music files). So, I need to undo the commit, but keep the source files, and I'll commit them later, when I have  nice tip: You can re-attach the branch to the commit that you removed it from with git branch -f  beginner, it isn't obvious what the difference is between the last two options (--soft and the one above it). Mentioning the index doesn't help, we don't really kno
 w what that means yet. @nessur's connection  to be told 'why' something works, than just to be told the answer. Kudos to this description - it helped be 'get' git.  also for the explanation. Question about this statement though (re --hard) : "your files are reset to their state at commit B". Say I had only committed some of my modifications, other files being intended for future commits. How much am I resetting? Just the committed files? so many people are supportive of the answer, I offer this feedback: write a quickly-readable and easily-executed set of instructions that I can run to fix my problem. The other answer has it; this one does not. This might not do what you expect if your erroneous commit was a (fast-forward)  is on a merge commit (ex: merged branch feature into master), git reset --hard~1 will point the master branch to the last commit inside the feature branch. In this case the specific commit ID should be used instead of the relative command. Upon further thought th
 is behaviour nay have been a result of merging the master branch into the feature branch first, testing and then (fast-forward) merging the feature branch that the number in HEAD~1 can be substituted to any positive integer, e.g. HEAD~3. It may seem obvious, but beginners (like me) are very careful when running git commands, so they may not want to risk messing something up by testing this stuff themselves.  comment on "what if you have already pushed the commit?". Is this answer still valid, or does that make it all more difficult? his is my understanding. First you deal with your repository locally. For git every repository so the state of the remote repo is irrelevant. Then, if you want to push the changes, it will complain that "Updates were rejected because the tip of your current branch is behind its remote counterpart". That is, if you did a hard reset. Then you can force the push with e.g. git push -f origin master (use with care).