On Thu, Mar 10, 2011 at 17:09, Julius Plenz <plenz@xxxxxxxxxxxxxxxx> wrote: > * Nguyen Thai Ngoc Duy <pclouds@xxxxxxxxx> [2011-03-10 17:00]: >> On Thu, Mar 10, 2011 at 10:19 PM, Julius Plenz <plenz@xxxxxxxxxxxxxxxx> wrote: >> > If you use libgit.a to perform reference resolutions on two or more >> > repositories that contain packed refs, cached_refs will store the packed >> > refs for the first repository to contain a packed-refs file only. >> >> If you use libgit.a to do anything on more than one repository, you >> get a lot more messed up that just that. Spawning a new process or >> accessing with libgit2 may be safer. Why do you want to do that in the >> first place? > > I was working on the cgit repository browser, where you have to peek > into several repositories to create the overview page. Since cgit > links to libgit.a I fixed the bug there. Not sure if that's the proper > way to do it, though... I never got around to answer your earlier email about this, but here is what I would have said ;) Since libgit.a doesn't work with multiple repos [1], cgit supports the use of an "agefile" (that's the option name in cgitrc) to obtain the last commit-date per repo. The content of such an agefile can be generated by a command like the following in one (or more) of your git hooks: git for-each-ref --sort=-authordate --format='%(authordate:iso8601)' --count=1 Hth. -- larsh [1] Even if libgit.a did support working with multiple repos in a single run, I probably would avoid this particular usage since it is bound to perform badly when lots of repos are involved (like on cgit.freedesktop.org), and even more so when the list is sorted by idle-time. Simply reading a small textfile per repo is much faster. -- 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