git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: Extremely slow progress during 'git reflog expire --all'
Date: Fri, 2 Apr 2010 23:50:19 +0200	[thread overview]
Message-ID: <201004022350.20999.elendil@planet.nl> (raw)
In-Reply-To: <20100402212858.GA28531@coredump.intra.peff.net>

On Friday 02 April 2010, Jeff King wrote:
> Can you reproduce the problem on your repo? If so, can you possibly tar
> it up and make it available (probably just the .git directory would be
> enough)?

Yes, I can reproduce. I've run it a few times and broke it off each time 
before it finished as I really had no idea how much longer it might take.

$ du -sh .git
1008M   .git

I can make that available, but it's going to take a while to upload and I 
don't want to leave it up too long as I'll be abusing a project service 
for that. So the people who want to look at it would have grab it fairly 
promptly (within 2 days or so).

Is that OK?

Cheers,
FJP

  reply	other threads:[~2010-04-02 21:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-02 19:54 Extremely slow progress during 'git reflog expire --all' Frans Pop
2010-04-02 21:28 ` Jeff King
2010-04-02 21:50   ` Frans Pop [this message]
2010-04-02 22:41     ` Jeff King
2010-04-03 14:29       ` Frans Pop
2010-04-03 20:33         ` Jeff King
2010-04-03 20:35         ` Jeff King
2010-04-04 18:22           ` Junio C Hamano
2010-04-05  6:26             ` Jeff King
2010-04-05 18:54               ` Junio C Hamano
2010-04-06  6:02                 ` Jeff King
2010-04-07 18:39                   ` Re*: " Junio C Hamano
2010-04-07 18:43                     ` Junio C Hamano
2010-04-08  7:00                       ` Jeff King
2010-04-08  6:52                     ` Jeff King

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=201004022350.20999.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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).