LKML Archive on
help / color / mirror / Atom feed
From: Jeff Garzik <>
To: Junio C Hamano <>
Subject: Re: [ANNOUNCE] GIT
Date: Sun, 09 Mar 2008 17:42:45 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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.


  reply	other threads:[~2008-03-09 21:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-23 21:07 [ANNOUNCE] GIT Junio C Hamano
2008-03-09 10:46 ` [ANNOUNCE] GIT Junio C Hamano
2008-03-09 16:56   ` Jeff Garzik
2008-03-09 20:28     ` Junio C Hamano
2008-03-09 21:42       ` Jeff Garzik [this message]
2008-03-10  6:34         ` Junio C Hamano
2008-03-11 19:11           ` Jeff Garzik

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: [ANNOUNCE] GIT' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).