Permalink
Browse files

Blog post import 3,4 of 32

  • Loading branch information...
mathias committed Apr 15, 2012
1 parent b61fa04 commit bc2c6308c0951f06b4c68d51bcecdad0e602064c
@@ -0,0 +1,34 @@
+---
+layout: post
+title: "Milwaukee DevHouse 1 Recap"
+date: 2008-03-19
+categories: blog_archive_project
+---
+
+(This post is part of my blog archiving project. This post appeared on
+[bytecodex.wordpress.com](http://bytecodex.wordpress.com/2008/03/19/milwaukee-devhouse1-recap/)
+on March 19, 2008.)
+
+[Pete Prodoehl has the
+scoop](http://rasterweb.net/raster/2008/03/18/milwaukeedevhouse1-wrap-up/).
+I don’t really know what to say about it. We all met up at Bucketworks
+in Milwaukee with the intent to hack and hang out. I got there at 6PM
+and left at around 5:30AM on the next day. It was quite the party.
+
+![devhouse
+photo](http://farm3.static.flickr.com/2106/2334180617_cb572b20ec.jpg?v=0)
+
+*(via [my flickr](http://flickr.com/photos/mattgauger/))*
+
+4braham started a twitter-events mashup project, and I unfortunately
+wasn’t much help with it.. I guess I’m too easily distracted. Other
+projects are detailed in Pete’s posts, I was actually out in the
+Bucketworks Flow room and so missed most of what went on in the smaller
+conference room.
+
+The light table where we did our plotting:
+
+![light table at
+bucketworks](http://farm4.static.flickr.com/3047/2334539597_e42fccdbe0.jpg?v=0)
+
+*(via [ashe’s flickr](http://flickr.com/photos/drydens/))*
@@ -0,0 +1,82 @@
+---
+layout: post
+title: "Git is full of win"
+date: 2008-03-28
+categories: blog_archive_project
+---
+
+(This post is part of my blog archiving project. This post appeared on
+[bytecodex.wordpress.com](http://bytecodex.wordpress.com/2008/03/23/git-is-full-of-win/)
+on March 23, 2008.)
+
+The blogosphere seems to be blowing up with regards to the SCM suite
+[git](http://git.or.cz/ "http://git.or.cz/"). At least, the blogosphere
+I frequent.
+
+git is an open source project started by Linus Torvalds and currently
+maintained by Junio Hamano, intended to replace the proprietary
+[BitKeeper](http://en.wikipedia.org/wiki/BitKeeper "Wikipedia - BitKeeper")
+system that the Linux kernel project used. Like
+[Monotone](http://www.monotone.ca/ "http://www.monotone.ca/") and
+[Mercurial](http://www.selenic.com/mercurial/wiki/ "http://www.selenic.com/mercurial/wiki/"),
+git is a modern decentralized revision control system that makes use of
+cryptography. The ‘repo’ doesn’t live on one server, instead every local
+copy on a developer’s machine is a full repo, with full version history.
+Developers initially copy the repo from somewhere (also known as
+branching or creating a clone) and make changes locally, commiting
+changes to their local repo as they code.
+
+The process of combining two branched repos in SCM is known as merging.
+When developers are ready to share their changes, they can ‘merge’ their
+work back into other developers’ trees, or others could pull down
+changes from the developer’s local repo and work from there. Merging was
+previously a time-consuming and frustrating task with other SCM tools,
+but git needed to be able to merge the repos of the Linux kernel
+developers fast. In fact, git makes it so much easier than previous SCM
+tools to branch and merge both local and remote repos that developers
+can keep several branches around locally for various changes to live in.
+
+The best
+[image I
+found](http://www.mcl.iis.u-tokyo.ac.jp/eng_version/index.html)
+to represent this style of passing around changes has nothing to do with
+version control, but gives a good idea if you think of ‘messages’ as the
+changes:
+
+![adhoc.jpg](http://bytecodex.files.wordpress.com/2008/03/adhoc.jpg?w=269&h=184)
+
+Because all the cool developers hack on laptops now.
+
+Usually while riding on bullet trains.
+
+Subversion & CVS, on the other hand, use a centralized server that all
+changes must be downloaded from and uploaded to; making concurrent work
+possible. But a centralized server may be restrictive if a development
+team is scattered across the globe (as in the Linux kernel team & most
+open source projects) rather than scattered across the cube farm. (As a
+side note: git does allow for public repo servers, but that is a whole
+‘nother topic.)
+
+Best of all, **git is fast**. [Faster than your
+filesystem](http://www.advogato.org/person/apenwarr/diary/371.html "Blog for apenwarr - Git is the next Unix"),
+in some cases. You can throw data in its repo & **10 years later it
+ensures you get the exact same file out**, due to cryptographic hash
+checking. SCM tools of years past couldn’t vouch for the integrity of
+your files, in fact checking in files was more likely to corrupt files
+at some future point, rather than protect them.
+
+I’m not going to go into all the features of git or why it’s faster,
+there’s [plenty of
+resources](http://robsanheim.com/2008/02/22/learn-git-10-different-ways/ "Panasonic Youth - Learn Git 10 Different Ways ") already.
+If you’ve used Subversion (svn) in the past, then [this
+tutorial](http://git.or.cz/course/svn.html "Git -SVN Crash Course") is
+probably your best bet.
+
+Since this turned into more of an overview of git rather than covering
+the two topics I had in mind when I started, look forward to two more
+posts this week: one on [GitHub](http://github.com/), a git repository
+hosting service, and [git-wiki](http://atonie.org/2008/02/git-wiki), a
+wiki intended for personal use that checks its changes into a local git
+repo.
+
+[](http://atonie.org/2008/02/git-wiki)

0 comments on commit bc2c630

Please sign in to comment.