On 11/10/07, Jakub Narebski <jnareb@xxxxxxxxx> wrote: > On Saturday, 10 November 2007, Jon Smirl wrote: > > On 11/10/07, Jon Smirl <jonsmirl@xxxxxxxxx> wrote: > >> On 11/9/07, Jakub Narebski <jnareb@xxxxxxxxx> wrote: > >>> Jon Smirl wrote: > >>> > >>>> At http://git.digispeaker.com/ the 'last change' column is not getting updated. > >>>> > >>>> mpc5200b.git > >>>> DigiSpeaker for Freescale MPC5200B. > >>>> Jon Smirl > >>>> 5 weeks ago > >>>> summary | shortlog | log | tree > >>>> > >>>> It still says 5 weeks ago, but if I click on the project last change is today. > >>>> > >>>> What controls this? I tried running update-server-info > >>> > >>> What does > >>> > >>> git for-each-ref --format="%(refname):%09%(committer)" --sort=-committerdate > >>> refs/heads > >> > >> [daedalus]$ git for-each-ref --format="%(refname):%09%(committer)" \ > >> --sort=-committerdate refs/heads > >> refs/heads/m24: Jon Smirl <jonsmirl@xxxxxxxxx> 1191362799 -0400 > >> refs/heads/m25: Jon Smirl <jonsmirl@xxxxxxxxx> 1191472422 -0400 > >> refs/heads/m26: Jon Smirl <jonsmirl@xxxxxxxxx> 1194382038 -0500 > >> refs/heads/m28: Jon Smirl <jonsmirl@xxxxxxxxx> 1194385071 -0500 > >> refs/heads/m29: Jon Smirl <jonsmirl@xxxxxxxxx> 1194585780 -0500 > > > > It appears to be using the first head instead of the most recent date. > It appears to not _sort_ the output by committerdate, as it should with > '--sort=-committerdate'. It is sorted by committerdate, the sort is ascending. Did you expect it to be descending, pick off the last entry instead of the first? > > 1442:[gitweb/web!git]$ git for-each-ref --format="%(refname):%09%(committer)" \ > --sort=-committerdate refs/heads > refs/heads/gitweb/web: Jakub Narebski <jnareb@xxxxxxxxx> 1194616779 +0100 > refs/heads/man: Junio C Hamano <junio@xxxxxxxxxxxxxxx> 1194602628 +0000 > refs/heads/html: Junio C Hamano <junio@xxxxxxxxxxxxxxx> 1194602626 +0000 > refs/heads/origin: Junio C Hamano <gitster@xxxxxxxxx> 1194602274 -0800 > [...] > refs/heads/gitweb-snapshot+navbar: Sven Verdoolaege <skimo@xxxxxxxxxx> 1134765981 +0100 > > 1443:[gitweb/web!git]$ git --version > git version 1.5.3.5 > > > Note that git-for-each-ref with those options returns most recent head > first, sorting output by date of commit (date of adding to repository) > > >>> > >>> return? Does adding --count select proper branch, with proper update > >>> date? > >> > >> Is it looking for master, and just picking the first branch instead? > > Gitweb should not (and I think does not) have 'master' hardcoded > anywhere. It might use HEAD in some cases you don't want it to... > > >>> > >>> Which gitweb version is this? > >> > >> <!-- git web interface version 1.5.3.5.605.g79fa-dirty, (C) 2005-2006, > >> Kay Sievers <kay.sievers@xxxxxxxx>, Christian Gierke --> > >> <!-- git core binaries version 1.5.3.5.605.g79fa-dirty --> > > Older version of gitweb used HEAD branch for'last changed' info on > the projects list page. That is why I asked about gitweb version. > > But this is not the case of your problem: > 1. Your gitweb is new enough to use git-for-each-ref. It use > git for-each-ref --format="%(committer)" --sort=-committerdate > --count=1 refs/heads > 2. Looking at 'heads' view (or 'heads' part of summary view) one can see > that m29 is current branch (HEAD), and it is most recent. > > Strange... > -- > Jakub Narebski > Poland > -- Jon Smirl jonsmirl@xxxxxxxxx - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
