git/list[1] front-page[2] threads[3] people[4] search[5] about
 

How to (re-)create .git/logs/refs

From
HSHolger Schurig <hs4233@mail.mn-solutions.de>
Date
May 8, 2008, 09:48 UTC
Message-ID
<200805081148.43657.hs4233@mail.mn-solutions.de>
Hi !

I have an old SVN project with lots of commits from 2005 to 2008 converted. This was a month ago. In the mean-time, I've made some commits from git as well.

"git log" shows both types of commit quite nicely.

"git checkout <sha1>" works also correctly, for arbitrary ancient SHA1s.

"git checkout @{2007-04-01}" doesn't work. I get an error like this:

  warning: Log for '' only goes back to Thu, 8 May 2008 09:35:38 +0000.
  fatal: bad object @{2007-04-01}

However, "git checkout @{2008-05-01}" works, because this commit come from git direct, not implicitly from SVN. It seems that neiver "git svn clone" nor "examples/git-svnimport.perl" creates/updates .git/logs/refs when it creates commits from an old SVN repository.

So my question:
a) is there a way to re-create .git/logs/refs ?
b) is there a simple way to get a list of ISO-dates and
   associated SHA1?  Then I could use a little python code to
   determine the SHA1 id that corresponds to some date (I need
   to access old versions of the source via bitbake and/or
   www.openembedded.org, so adding a custom fetch method with
   some python magic is a non-brainer).
Message 1 of 1 in “How to (re-)create .git/logs/refs”
  1. Holger SchurigMay 8, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.