I've actually gotten to the point where I git repo everything I do. It takes seconds, and being able to cheaply branch to try different things is indispensable.
I've heard the argument that people don't want to use Github because the free version "exposes" your code, but for all practical purposes, this is bunk. It's hard enough to understand *documented* source code. On Sun, Mar 28, 2010 at 6:46 AM, Tim Hoffman <[email protected]> wrote: > No probs didn't think you where too harsh, just a different opinion. > > On Mar 28, 8:58 pm, Baz <[email protected]> wrote: > > Now we're talking! Sorry I came off a little harsh, I just wasn't into > > calling him a non-serious developer because he wanted to get at his > > own code. I don't create a git repo for every little file I make (even > > though I probably should!), and maybe his code is just for > > experimentation without big security needs. Or maybe he forgot to > > commit! Anyway, I agree with you guys about the security. > > Yep I do that too. If it's micky mouse stuff but I don't want to lose > it > I tar it up and stick it in gmail, or docs. > > T > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Ikai Lan Developer Programs Engineer, Google App Engine http://googleappengine.blogspot.com | http://twitter.com/app_engine -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
