On 10 December 2014 at 16:07, Junio C Hamano wrote:
> Jeff King writes:
>>> git reflog expire --expire=now --all && git gc --prune=now --aggressive
>>>
>>> Maybe:
>>>
>>> git gc --purge
>>
>> Yeah, that is common enough that it might be worthwhile (you probably
>> want --expire-unreachable in the
Jeff King writes:
>> ... I'd be happy to
>> contribute a patch that gives 'gc' a flag to do the equivalent of:
>>
>> git reflog expire --expire=now --all && git gc --prune=now --aggressive
>>
>> Maybe:
>>
>> git gc --purge
>
> Yeah, that is common enough that it might be worthwhile (you probab
On Tue, Dec 09, 2014 at 10:15:31PM +, Roberto Tyley wrote:
> > Not that I expect you to want to work on filter-branch. :) But maybe
> > food for thought for a BFG feature.
>
> I haven't heard much demand for a recover/restore feature on the BFG
> (I think by the time people get to the BFG, th
On Tuesday, 9 December 2014, Jeff King wrote:
> I actually think filter-branch's "refs/original" is a bit outdated at
> this point. The information is there in the reflogs already, and
> dealing with refs/original often causes confusion in my experience. It
> could probably use a "git filter-branc
On Tue, Dec 09, 2014 at 04:01:50PM +, Roberto Tyley wrote:
> > I also don't know if BFG keeps backup refs around (filter-branch, for
> > example, writes a copy of the original refs into refs/original; you
> > would want to delete that if you're trying to slim down the repo).
>
> The BFG repor
On 9 December 2014 at 14:14, Jeff King wrote:
> On Mon, Dec 08, 2014 at 05:22:23PM +0100, Martin Scherer wrote:
>
>> # invoke bfg --delete-folders something multiple times with different
>> pattern.
>>
>> # try to cleanup
>>
>> git gc --aggressive --prune=now # big blobs still in history
>> git fs
On Mon, Dec 08, 2014 at 05:22:23PM +0100, Martin Scherer wrote:
> # invoke bfg --delete-folders something multiple times with different
> pattern.
>
> # try to cleanup
>
> git gc --aggressive --prune=now # big blobs still in history
> git fsck # no results
> git fsck --full --unreachable --dang
Hi Martin, I'm the developer of the BFG - I'd guess that there
probably isn't a bug for Git developers here, so you might want to
open one or more issues at
https://github.com/rtyley/bfg-repo-cleaner/issues, where I'd be happy
to take a look.
best regards,
Roberto
> On 8 Dec 2014 16:35, "Martin S
Hi,
after using BFG on a repo given certain directory globs, all of those
files(names) are gone from history, but can not be collected by garbage
collection anymore. So the blobs of the underlying files are not deleted
and only the file names are not associated with the blob anymore. I
wonder, if
9 matches
Mail list logo
