Re: Deprecation/Removal schedule

> On 2/5/07, Shawn O. Pearce <spearce@spearce.org> wrote:
> > Alex Riesen <raa.lkml@gmail.com> wrote:
> > > On 2/5/07, Shawn O. Pearce <spearce@spearce.org> wrote:
> > > >I use it daily.  Mainly `git log origin/master@{1}..origin/master`
> > > >to see what has come in from Junio since my last fetch.  The @{n}
> > > >syntax has (for me) been one of its best features.  (Thanks Junio!)
> > >
> > > It looks and smells like a useful feature. I just haven't found
> > > any use for it yet. Besides all the good, it's another part of a repo
> > > needing maintenance (constantly growing thing, like /var/log).
> > 
> > `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.