[lkml]   [2008]   [Mar]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Junio C Hamano wrote:
> Jeff Garzik <> writes:
>> Junio C Hamano wrote:
>>> The latest maintenance release GIT is available at the
>>> usual places:
>>> git-{gz,bz2} (tarball)
>>> git-htmldocs-{gz,bz2} (preformatted docs)
>>> git-manpages-{gz,bz2} (preformatted docs)
>>> RPMS/$arch/git-*-$arch.rpm (RPM)
>> Does it address the following issue, present in git-core-
> I do not think so.
> Is it really an issue, or is it just a warning message unread/unfollowed?

It's not a warning message, it is an annoying delay that has been added
to almost -every- local pull, impacting my main kernel workflow.

Further -- as my email demonstrated with examples -- it would repeatedly
'git gc' on the same repository over and over again, for each 'git pull'
or 'git rebase' that I did. That is overly excessive.

> I am comparing the last line you quoted from the command output in that
> message, which suggests the user to run 'git prune', and your comment on
> the next line in that message that says "I regularly run 'git gc'", and
> scratching my head. I cannot tell if you regularly run 'git prune' or not
> from it...

Yes, I regularly run both 'git gc' and 'git prune'.

But since (ref original email) I was doing some rebasing, there are
inevitably changesets left dangling after such an operation.


 \ /
  Last update: 2008-03-09 22:45    [W:0.064 / U:1.784 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site