From: Linus Torvalds <torvalds@linux-foundation.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Brandon Casey <casey@nrlssc.navy.mil>,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: "git reflog expire --all" very slow
Date: Mon, 30 Mar 2009 22:42:50 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0903302239040.4093@localhost.localdomain> (raw)
In-Reply-To: <7vy6um6z9m.fsf@gitster.siamese.dyndns.org>
On Mon, 30 Mar 2009, Junio C Hamano wrote:
>
> I do have a lot of reflog entries kept around, as my main repository has
> these:
>
> [gc]
> reflogexpire = '2005-01-01 00:00:00 +0000'
> reflogexpireunreachable = '2005-01-01 00:00:00 +0000'
I think that actually _hides_ the problem. You'll never have anything at
all that triggers that
if (timestamp < cb->cmd->expire_unreachable) {
because your "expire_unreachable" timestamp is already very old (== small
value), so 'timestamp' will _not_ be older (smaller value) than that.
I dunno. As mentioned, I don't really understand why we'd want to save
some of those reflog entries at all in the first place, so I'm probably
missing something.
If we've asked for reflog entries past a certain age to be expired, why do
when then look at the details of those reflog entries and only expire them
under certain circumstances? Just expire them, and get rid of the
'unreachable' part.
Linus
next prev parent reply other threads:[~2009-03-31 5:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 1:43 "git reflog expire --all" very slow Linus Torvalds
2009-03-31 4:34 ` Junio C Hamano
2009-03-31 5:09 ` Linus Torvalds
2009-03-31 5:24 ` Junio C Hamano
2009-03-31 5:42 ` Linus Torvalds [this message]
2009-03-31 5:57 ` Junio C Hamano
2009-03-31 5:50 ` Junio C Hamano
2009-03-31 5:38 ` Linus Torvalds
2009-03-31 5:50 ` Linus Torvalds
2009-03-31 5:51 ` Linus Torvalds
2009-04-02 6:46 ` Junio C Hamano
2009-04-02 15:30 ` Linus Torvalds
2009-03-31 6:08 ` Junio C Hamano
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.2.00.0903302239040.4093@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=casey@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.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).