Subject: DocOz Episode: Shed fat (7 days)

From: Lose the Extra Flab <[email-masked]>
Date: Thu, 03 Jul 2014 11:01:52 -0700

Episode Recap: Shed Fat in a way that Fits Your Schedule

On Today's Episode -

DocOz is showing you how you can be burning fat all day long

- w/out working out
- w/out changing your diet

View Episode Explanation: http://www.banartfax.com/live-stream/episode/oz.video

If you can carve out 1 minute a day, you can shed 1lb per day.

[Oz Blog]

To stop further episode recaps - go here http://www.banartfax.com/3irjt.g4i4 or write "stop" to Current Update Alerts
1644 Doral Drive-Brookings, SD 57006

-
-
-
-
-
-
-
 -assumed you meant a gist - seeing as the official github project for .gitignores was unmaintained and refusing su-bmissions last time I looked (IIRC there were 200 ignored pull requests, and a huge number of Issues that  I just noticed a problem with this. I was doing some git acrobatics, and when I checkout out back to master and applied my stashed changes, I had lost my saved build schemes! fortunately, I had backed them up, just in case... but the solution is to ignore a little more specifically inside the xcuserdata directory. I changed I also suggest to add .svn for projects that work with both source control systems  I had lost my saved build schemes! " -- argh! That's what I was trying to avoid! Sorry :(. I've added an exception for "xcschemes" which seems to be what my Xcode is using   I can see that helping for some projects, but using one project with two SCM's sounds very unusual (dangerous in many ways). I've been on projects where we did it deliberately - but 9 times i
 n 10 when I've seen it, it was an accident. In most cases, I think it's a major bug / mistake to have two SCM's versioning one set of files, so I'd rather leave the .svn folder in there -- for most people, they'll see all the .svn files appear and go  and realise their mistake. In general you are right - there is almost no reason to work with 2 SCMs on one project. But I have personally used this approach several times. The most common (for me) case was when a client gives me his existing project with SVN. I work with GIT. I think that there was no project where SVN worked 100% well for me - there are always problems with it. This is why I always create my own git repository for all the ongoing commits and ignore the .svn folders. Eventually I commit all the changes to client's SVN and forget about it.   I added cocoapods to the mix   cannyboy Feb 8 '13 at 12:40"the syntax for is very hard to understand" you serious ?? its an easy pattern system it took about 2 minutes to understand
  it.. iv'e seen much worse things