Ariejan.net

Git is quite common nowadays and a lot of people are asking me how they can create a patch file. Creating a patch file with git is quite easy to do, you just need to see how it’s done a few times.

This article will show you how to create a patch from the last few commits in your repository. Next, I’ll also show you how you can correctly apply this patch to another repository.

I got git problem: error: unable to create temporary sha1 filename when pushing to a remote repository. The fix is rather easy.

Today I had the very pleasure of giving Codaset.com a try! Codaset is being developed by Joel Moss in Ruby on Rails and could be a real Github killer!

Just as a kind of mini cheat sheet for using git tags. Jörg Mittag had some great additions that weren’t in the original post which warrant a new post.

Git has three different type of tags:

• Lightweight tags
• Annotated tags
• Signed tags

Let’s start with lightweight tags.

Lightweight tags

Just as a kind of mini cheat sheet for using git tags:

Adding a tag:

• git tag tag_name
• git tag
  Should show your new tag.
• git push origin --tags or git push origin :tag_name
  Because git push doesn’t push tags.

Removing a tag:

• git tag -d tag_name
• git tag
  Should no longer show your tag.
• git push origin :refs/tags/tag_name
  Because git push --tags doesn’t push deleted tags.

I haven’t seen a schedule yet, but I’ve been told by Mark that I’ll be speaking at Rails Underground this year.

My talk will be on the topic of Git. In about 45 minutes time I’ll show you all the basic git features you’ll need on a daily basis. Not only that, but I’ll also explain how git manages all those commits and branches so you can be on your way to become a git power user.

Git is quite an awesome version control system. Why? Because it’s lightning fast, even for large projects (among other reasons).

But, how do you use Git effectively for development on a daily basis? Let me explain to you.

Branches

There’s a lot of cool stuff pooring in about what’s new in Rails Edge (which will become Rails 2.3 and/or Rails 3).

Most likely you can’t wait to get started with these new features, especially when you’re about to start a new project, which doesn’t have to be stable yet, but will be by the time 2.3/3.0 come out. This post shows you the way to create a new Rails app based on the most current Rails code, also called Edge Rails.

I bet the following has happened to you: you are happily working on a project and are in the middle of something. You are not ready to commit your changes, because you your tests don’t pass yet. Then your client calls with a bug report that needs to be fixed right now. (You know how clients can be.)