From: Nicolas Pitre <nico@cam.org>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: How to (re-)create .git/logs/refs
Date: Thu, 08 May 2008 13:28:50 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0805081313190.23581@xanadu.home> (raw)
In-Reply-To: <200805081256.11465.hs4233@mail.mn-solutions.de>
On Thu, 8 May 2008, Holger Schurig wrote:
> So my question:
>
> a) is there a way to re-create .git/logs/refs ?
No.
The reflog records how _you_ modified your various branches locally.
This has no direct relationship with the dates the commits in those
branches were created. It records what was your own view of the
repository in time. So if you performed an import of a SVN repository
last week, then it is normal that you don't have any view into that
particular repository's state before last week.
> 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).
Have a look at the documentation for the --pretty=format option in the
git-log man page. For example:
git log --pretty=format:"%H %ai"
might be just what you're looking for.
Nicolas
next prev parent reply other threads:[~2008-05-08 17:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2008-05-08 9:48 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=alpine.LFD.1.10.0805081313190.23581@xanadu.home \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=hs4233@mail.mn-solutions.de \
/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).