Re: dangling commits

From: Marco Roeland <marco.roeland@xs4all.nl>
Date: Jan 16, 2006, 10:08 UTC
Message-ID: <20060116100814.GA5196@fiberbit.xs4all.nl>
In-Reply-To: <20060116093249.8F939353A3F@atlas.denx.de>

On Monday January 16th 2006 Wolfgang Denk wrote:

> I like to have  my  repository  "clean"  so  there  are  no  warnings
> normally  from  git-fsck-objects  -  if  you  get used to expect some
> "harmless" messages you might easily miss a critical error.

That's right, yes.

> > However you can easily get rid of them by using "git prune".
> 
> Tried this, didn't work.

Ok, didn't know that it didn't prune directly from packs. I should have realised that it only can do so efficiently by repacking I suppose.

> Ummm... please have a look at the  .git/objects/pack/  directory  for
> example in your Linux repository.

I did as a matter of fact, but I use "git" as protocol and also regularly "repack" the repository, when I'm not using the machine for a while, to make 'gitk' and 'qgit' work faster. It is less apparent then! Thanks very much for clearing up my knowledge. It only shows the power of git that even ignorant gits like myself still find it useful and productive. There's just enough rope to wiggle yourself out of precarious situations but fortunately most of the time not enough to hang yourself.

-- 
Marco Roeland