Posts Tagged ‘ git ’

Fixing CentOS Root Certificate Authority Issues

Wednesday, June 1st, 2011

While trying to clone a repository from Github the other day on one of my EC2 servers and I ran into an SSL verification issue. As it turns out, Github renewed their SSL certificate (as people who are responsible about their web presence do when their certificate is about to expire). As a result, I couldn’t git clone over https. This presents a problem since all my deploys work using git clone over https.

Git Command Aliases

Monday, December 28th, 2009

This is kind of a tip of the day, but I just think its cool so I am sharing it with everyone. And being a recent convert to Git and the fact that I have to use Subversion at my place of work, I find myself constantly doing things like this out of habit.

$ git st  && git ci

Well now I can do that (although it may not be a good idea) with git alias:

elubow@beacon (master) supportskydivers$ git config --global status
elubow@beacon (master) supportskydivers$ git config --global commit
elubow@beacon (master) supportskydivers$ git st && git ci
# On branch master
nothing to commit (working directory clean)

Now st and ci are git aliases for status and commit respectively.

Git Branch Name in Your Bash Prompt

Friday, December 11th, 2009

I work with a few repositories at any given time. And during that time, I typically have multiple branches created for each repository. I figured that it would make my life easier if I knew which branch and/or repository I was working in. Luckily, very little hackery is required here since the git distribution already comes with such a tool. (Note: If you didn’t build Git from source, then you may not have this file.)

Converting From Subversion To Git

Monday, November 16th, 2009

Now that I have basically fallen for Git, I decided to finally move my Subversion repository over to Git (this way I can finally have a remote backup of it that I am comfortable with on Codaset).

The method for this was a lot more straightforward than I expected it to be. For the conversion tool, I used Nirvdrums fork of svn2git. It a feature complete version of the svn2git portion though the rest of it is still is development. Since it is a Ruby gem, getting it installed was a breeze. Just make sure that you have Ruby and rubygems installed.

Remote Code Storage

Monday, November 9th, 2009

I was chatting with a friend of mine the other day about version control and why it’s necessary. So I decided to throw together a few options and a little explanation about why its important.

I have been using version control in some form or another for many years. I started with CVS, then moved to Subversion (which I still use quite a bit), and now, as my latest post about Git GUI’s on the Mac suggests, I have moved to Git. The one thing that has been consistent across every single transition has been that I had some sort of remote code storage every time. During the CVS days, I used a CVS pserver and stored my code locally and remotely for safety (and ease of checkout/deployment). For subversion, I always stored my code locally and used an apache install somewhere with a WebDAV module to get at and deploy whatever code is necessary.

Ultimately I use remote code storage for 2 reasons, back up my existing code base (so I have it in more than one place) and to have a visualization of what is going on in your project. That visualization is handy to be used as a central consistent view for multiple people (unlike a personal client which can be different per user).

Git GUI on Mac OS X

Friday, November 6th, 2009

I have been using Git a lot lately and have found a lot of things I like better in Git than in Subversion. The one major item that was really bothering me was that there wasn’t really too many Git clients that could help you visualize the repository. I mean show merges, commits, branching, blame, etc. Seeing that CVS and Subversion have been around for a lot longer, there are many clients for them and now that I have been using Git for a while on the command line, I decided to take a look again.

What I am looking for is simple. I want 2 things:

  1. In the typical Mac style, I want a great looking interface. I want to be able to see who did what, when, and why (assuming good commit messages from the developers).
  2. Easy navigation through all the features. I am not planning on using any of the commands visually, I am still an archaic command line junkie.

One of my favorite features of git coming from Subversion is the ease of branching. I branch for everything now that I am using git. So in order to best track my changes, I was hoping for something to help me visualize my branches. I didn’t count this specifically in my desires because it wasn’t a requirement to be acceptable, but it definitely would have helped to tip the scales.