One of my esteemed prior co-workers recommends that I follow git releases very closely. I've added a "git-update" command into my path so I can just say "git update" occasionally to get all the newest features and bugs.
#!/bin/bash
(
set -e
cd $HOME/src/git
export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
git fetch
git clean -xdf
git reset --hard
git merge origin/master
make configure
sh configure --prefix=/opt/git
make all doc
sudo make install install-doc install-html
)
nice but why? (Score:1)
One of my esteemed prior co-workers recommends that I follow git releases very closely.
Is git not yet stable? Is the bleeding edge still needed? For whom? Or is what a distro package manager (eg Ubuntu Paunty or Intrepid
apt-get .debs) provides good enough for most folks?I've added a "git-update" command into my path so I can just say "git update" occasionally
Nice. That ability to extend it simply is awesome.
Since I would expect
git-updateto operate against the remote repo for the current project directory, i might name thisgit-gitupdateon my system to avoid misunderstanding.to get all the newest features and bugs.
how good / bad is the features / bugs ratio?
Bill
# I had a sig when sigs were cool
use Sig;
Re: (Score:1)
It pretty much just works so I don't worry about the bugs that much. My Ubuntu only goes up to 1.6.0.4 and I'm currently on 1.6.4.rc2. I forget what happened but I'm fairly sure I want to be at 1.6.2+.