From: Petr Baudis <pasky@suse•cz>
To: "MichaelTiloDressel@t-online•de" <MichaelTiloDressel@t-online•de>
Cc: git@vger•kernel.org
Subject: Re: git-gc --prune interferes cogito?
Date: Wed, 17 Oct 2007 17:38:41 +0200 [thread overview]
Message-ID: <20071017153841.GL18279@machine.or.cz> (raw)
In-Reply-To: <1IiA7L-1AWmmW0@fwd35.aul.t-online.de>
Hi,
On Wed, Oct 17, 2007 at 04:43:27PM +0200, MichaelTiloDressel@t-online•de wrote:
> I'm using git-1.5.3.2 and cogito-0.18.1.
>
> After I did a git-gc --prune cg-status didn't show my branches anymore.
> git-branch -a still showed the branches.
> I think that git-gc removed all files from .git/refs/heads/ except for
> origin. Git seams to be fine with the branches in
> .git/logs/refs/heads/.
>
> So should git-gc not be used together with cogito?
Cogito doesn't support packed heads - I guess setting gc.packrefs to
false should fix the issue. Cogito should support packed tags, I guess;
I don't know if there's a way to make git-gc pack only tags.
--
Petr "Pasky" Baudis
Early to rise and early to bed makes a male healthy and wealthy and dead.
-- James Thurber
next prev parent reply other threads:[~2007-10-17 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 14:43 git-gc --prune interferes cogito? MichaelTiloDressel
2007-10-17 15:38 ` Petr Baudis [this message]
2007-10-17 18:55 ` Michael Dressel
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=20071017153841.GL18279@machine.or.cz \
--to=pasky@suse$(echo .)cz \
--cc=MichaelTiloDressel@t-online$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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