From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
"Jakub Narebski" <jnareb@gmail.com>,
git@vger.kernel.org
Subject: Re: Deprecation/Removal schedule
Date: Tue, 6 Feb 2007 14:01:52 +0100 [thread overview]
Message-ID: <81b0412b0702060501u41a3f707pea4bfc58220fd862@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0702061144430.22628@wbgn013.biozentrum.uni-wuerzburg.de>
On 2/6/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > >
> > > `git gc` is your friend. It automatically trims the reflogs, keeping
> > > only the last 90 days worth of entries. You can tune this with the
> > > `gc.reflogexpire` configuration parameter.
> >
> > git gc (repack -d of it) is too dangerous in a shared repo: it breaks
> > the repos which depend on the master repository, have sent (by some
> > means) some objects over to the master, and accidentally removed
> > the reference, and were pruned afterwards.
>
> We no longer call git-prune automatically in git-gc. You have to say
> "git-gc --prune" to trigger that behaviour.
no. You'd have to stop calling repack as well.
I mean the objects that generally have to be removed and just
accidentally was not pinned in the shared repo.
Or did you mean that repack will leave unreferenced objects
behind in objects/??/files?
next prev parent reply other threads:[~2007-02-06 13:02 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 6:48 Deprecation/Removal schedule Junio C Hamano
2007-02-05 6:57 ` Shawn O. Pearce
2007-02-05 9:33 ` Jakub Narebski
2007-02-05 10:11 ` Jakub Narebski
2007-02-05 10:25 ` Shawn O. Pearce
2007-02-05 15:50 ` Alex Riesen
2007-02-05 19:45 ` Shawn O. Pearce
2007-02-05 22:49 ` Alex Riesen
2007-02-05 22:55 ` Shawn O. Pearce
2007-02-06 10:20 ` Alex Riesen
2007-02-06 10:45 ` Johannes Schindelin
2007-02-06 11:00 ` Jeff King
2007-02-06 11:03 ` Johannes Schindelin
2007-02-06 13:09 ` Alex Riesen
2007-02-06 13:24 ` Johannes Schindelin
2007-02-06 13:32 ` Alex Riesen
2007-02-06 13:01 ` Alex Riesen [this message]
2007-02-05 12:00 ` Mark Wooding
2007-02-05 12:45 ` Johannes Schindelin
2007-02-05 15:53 ` Alex Riesen
2007-02-05 16:26 ` Linus Torvalds
2007-02-05 17:56 ` Junio C Hamano
2007-02-05 19:24 ` [PATCH] Add --patchdepth parameter to git-am.sh Andy Parkins
2007-02-05 19:37 ` Shawn O. Pearce
2007-02-07 8:27 ` Junio C Hamano
2007-02-07 9:44 ` Jakub Narebski
2007-02-07 9:59 ` Andy Parkins
2007-02-06 14:55 ` Deprecation/Removal schedule Andreas Ericsson
2007-02-06 15:26 ` Alex Riesen
2007-02-06 15:33 ` Johannes Schindelin
2007-02-07 7:12 ` Junio C Hamano
2007-02-07 8:33 ` Jakub Narebski
2007-02-07 9:33 ` Johannes Schindelin
2007-02-07 10:13 ` Jakub Narebski
2007-02-07 9:37 ` Junio C Hamano
2007-02-07 11:10 ` Johannes Schindelin
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=81b0412b0702060501u41a3f707pea4bfc58220fd862@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=spearce@spearce.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).