Messages in this thread | | | Date | Sun, 09 Mar 2008 17:42:45 -0400 | From | Jeff Garzik <> | Subject | Re: [ANNOUNCE] GIT 1.5.4.4 |
| |
Junio C Hamano wrote: > Jeff Garzik <jeff@garzik.org> writes: > >> Junio C Hamano wrote: >>> The latest maintenance release GIT 1.5.4.4 is available at the >>> usual places: >>> >>> http://www.kernel.org/pub/software/scm/git/ >>> >>> git-1.5.4.4.tar.{gz,bz2} (tarball) >>> git-htmldocs-1.5.4.4.tar.{gz,bz2} (preformatted docs) >>> git-manpages-1.5.4.4.tar.{gz,bz2} (preformatted docs) >>> RPMS/$arch/git-*-1.5.4.4-1.$arch.rpm (RPM) >> Does it address the following issue, present in git-core-1.5.4.1-1.fc8? >> >> http://marc.info/?l=git&m=120423022832530&w=2 > > 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.
Jeff
| |