hmmm.... i just assumed it wouldn't be necessary to check out the most current code before checking out the release prior to the most current code
let me see if i understand what's going on 1) git clone git://git.gnome.org/gnumeric this creates a source tree with the most current checked in code 2) git checkout GNUMERIC_1_9_6 this backs up in time to the tag, leaving my source tree at 1.9.6 3) git checkout -b R196 this creates a local branch called R196, with the source tree at 1.9.6 from then on i can switch back an forth with "git checkout master" and "git checkout R196" On Fri, May 1, 2009 at 3:17 PM, Emmanuel Pacaud <emmanuel.pac...@lapp.in2p3.fr> wrote: > Hi, > > Le vendredi 01 mai 2009 à 14:20 -0400, Marlon Nelson a écrit : >> $ git clone -n git://git.gnome.org/gnumeric > > Why are you using -n here ? Remove it and the following commands should > work as expected... > >> Initialized empty Git repository in /home/marlon/gnome-dev/gnumeric/.git/ >> remote: Counting objects: 164330, done. >> remote: Compressing objects: 100% (24273/24273), done. >> remote: Total 164330 (delta 139555), reused 163265 (delta 138753) >> Receiving objects: 100% (164330/164330), 118.08 MiB | 188 KiB/s, done. >> Resolving deltas: 100% (139555/139555), done. >> $ cd gnumeric > > If you don't want to clone the gnumeric repository again without -n, > just do git checkout master here. > >> $ git checkout GNUMERIC_1_9_6 >> error: Entry 'ChangeLog' would be overwritten by merge. Cannot merge. >> $ > >> i guess i'm supposed to read all the man pages and become a git >> expert, in order to be able to grab the latest release to compile > > No need to be a git expert, you can also use the following file: > > http://ftp.gnome.org/pub/gnome/sources/gnumeric/1.9/gnumeric-1.9.6.tar.gz > > Emmanuel. > > > -- -eom- _______________________________________________ gnumeric-list mailing list gnumeric-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnumeric-list
