All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: git@vger.kernel.org, Nicolas Pitre <nico@cam.org>
Subject: Re: How to (re-)create .git/logs/refs
Date: Tue, 13 May 2008 11:38:38 +0200	[thread overview]
Message-ID: <4829619E.4020701@op5.se> (raw)
In-Reply-To: <200805131111.42517.hs4233@mail.mn-solutions.de>

Holger Schurig wrote:
>> 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 would be alot slower for large projects. Otoh it would also mean
it'd work on a freshly cloned repository, so perhaps it's worth
the trade-off.


>  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.
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

  reply	other threads:[~2008-05-13  9:39 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
2008-05-13  9:38       ` Andreas Ericsson [this message]
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=4829619E.4020701@op5.se \
    --to=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=hs4233@mail.mn-solutions.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.