From: Michael Gebetsroither <gebi@sbox.tugraz.at>
To: git@vger.kernel.org
Subject: Re: [BUG] git-gui loose object warning every hour
Date: Fri, 20 Jun 2008 02:40:25 +0200 [thread overview]
Message-ID: <g3eu9p$j8k$2@ger.gmane.org> (raw)
In-Reply-To: 20080620003216.GR11793@spearce.org
* Shawn O. Pearce <spearce@spearce.org> wrote:
> Michael Gebetsroither <gebi@sbox.tugraz.at> wrote:
>> The loose object warning from git-gui poped up 3 times in the last 4
>> hours (i've gc'ed the repo every time).
>
> This isn't a per-hour warning. What's happening is there are loose
> objects which git-gc has not pruned away. Try running git-prune in
> the repository to decrease the loose object count.
I've clicked yes (to remove the loose objects) on every popup of the
loose object warning dialog.
>> I've already set gc.auto=0 so i do _NOT_ want git to do anything
>> automatically.
>
> Hmm. Maybe git-gui should look at this flag on startup and if set
> simply not perform the loose object count check.
That would be nice, yes.
cu,
michael
--
It's already too late!
prev parent reply other threads:[~2008-06-20 0:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 0:21 [BUG] git-gui loose object warning every hour Michael Gebetsroither
2008-06-20 0:32 ` Shawn O. Pearce
2008-06-20 0:40 ` Michael Gebetsroither [this message]
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='g3eu9p$j8k$2@ger.gmane.org' \
--to=gebi@sbox.tugraz.at \
--cc=git@vger.kernel.org \
/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).