From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: git@vger.kernel.org
Cc: Nicolas Pitre <nico@cam.org>
Subject: Re: How to (re-)create .git/logs/refs
Date: Tue, 13 May 2008 11:11:42 +0200 [thread overview]
Message-ID: <200805131111.42517.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <200805130842.06112.hs4233@mail.mn-solutions.de>
> Okay, then I presume it's a shortcoming that the @{date}
> syntax uses .git/logs/ref.
Is there any reason sha1_name.c (which is responsible for the @{}
syntax) doesn't include list-objects.h and uses
traverse_commit_list() for it's purposes? It wouldn't then need
to use .git/logs/ref anymore.
If that would be ok, then maybe I find time (in my spare time)
and prepare a patch in this direction.
next prev parent reply other threads:[~2008-05-13 9:15 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
2008-05-13 6:42 ` Holger Schurig
2008-05-13 9:11 ` Holger Schurig [this message]
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=200805131111.42517.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=git@vger.kernel.org \
--cc=nico@cam.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).