Re: Trying to use git-filter-branch to compress history by removing large, obsolete binary files

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Dmitry Potapov <dpotapov@...>
Cc: Elijah Newren <newren@...>, Alex Riesen <raa.lkml@...>, Frank Lichtenheld <frank@...>, <git@...>
Date: Monday, October 8, 2007 - 5:27 am

Dmitry Potapov wrote:

git-rebase being the most common culprit, right alongside 'git commit --amend'.


A clone only fetches revs reachable from a ref, so pruning immediately
after a clone is completely pointless.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: Trying to use git-filter-branch to compress history by r..., Johannes Schindelin, (Sun Oct 7, 7:19 pm)
Re: Trying to use git-filter-branch to compress history by r..., Johannes Schindelin, (Sun Oct 7, 7:28 pm)
Re: Trying to use git-filter-branch to compress history by r..., Johannes Schindelin, (Sun Oct 7, 8:34 pm)
Re: Trying to use git-filter-branch to compress history by r..., Johannes Schindelin, (Sun Oct 7, 9:06 pm)
Re: Trying to use git-filter-branch to compress history by r..., Johannes Schindelin, (Tue Oct 9, 6:37 am)
Re: Trying to use git-filter-branch to compress history by r..., Andreas Ericsson, (Mon Oct 8, 5:27 am)