I'm not sure to understand. So please, excuse me if I offense you with trivial details.
If you feel to be up to date via gitk but your last commit is 1 month old, I fear you're not up to date at all. As Git is a distributed version control system, you have to keep your copy of the HISTORY in sync with any other reference. To do this, you have to run "git pull" or "git fetch". Perhaps could you read: http://sourceforge.net/apps/mediawiki/viking/index.php?title=Using_git_to_hack_on_and_contribute_to_Viking#Update_from_upstream http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html Regards, Guilhem. Le mercredi 22 juillet 2009 à 17:50 -0600, Scofield, Tim a écrit : > On 07/22/2009 12:09 PM, Guilhem BONNEFILLE wrote: > > But I'm surprised with your result as the commit you displayed in your > > email is an old one (Cf. its date). > > What command do you use to update your repo? > > > I haven't gotten that far yet. I ran "git clone > git://viking.git.sourceforge.net/gitroot/viking" on July 16th. > > If not done yet, you can run "gitk --all" to check relations between > > remote branches and local branches > Since I haven't added any remote branches yet, it looks up to date per gitk. > > Tim > > ------------------------------------------------------------------------------ > _______________________________________________ > Viking-devel mailing list > Viking-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/viking-devel > Viking home page: http://viking.sf.net/ ------------------------------------------------------------------------------ _______________________________________________ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
