From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: git@vger.kernel.org
Subject: How to (re-)create .git/logs/refs
Date: Thu, 8 May 2008 11:48:43 +0200 [thread overview]
Message-ID: <200805081148.43657.hs4233@mail.mn-solutions.de> (raw)
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).
next reply other threads:[~2008-05-08 10:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 9:48 Holger Schurig [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-08 10:56 How to (re-)create .git/logs/refs Holger Schurig
2008-05-08 12:28 ` Holger Schurig
2008-05-08 17:28 ` Nicolas Pitre
2008-05-13 6:42 ` Holger Schurig
2008-05-13 9:11 ` Holger Schurig
2008-05-13 9:38 ` Andreas Ericsson
2008-05-13 11:46 ` Johannes Schindelin
2008-05-13 12:13 ` Holger Schurig
2008-05-13 13:24 ` Jakub Narebski
2008-05-13 13:50 ` Holger Schurig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200805081148.43657.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).