Re: limiting git branch --contains
- From
Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
- Date
- Mar 25, 2023, 08:05 UTC
- Message-ID
- <ZB6rXKOjOI40khj1@ugly>
- In-Reply-To
- <20230325063035.GA562387@coredump.intra.peff.net>
On Sat, Mar 25, 2023 at 02:30:35AM -0400, Jeff King wrote:
> Nobody has yet; you could be that someone. ;) >
damn ;)
Show 6 quoted lines
>I do think there might be some complications, though. I think we may >build commit graphs by default these days during "gc" and even >incrementally after "fetch". If we warned when the graphs are disabled, >it basically means that every command in a repo with replace refs would >issue the warning. >
yeah, i thought about that, too ...
it would be easy enough to squelch the warning by manually disabling writing or using the graph. the downside is that if the root cause gets fixed, the user would be still missing out (unless they read the changelog and remembered to reconfigure all affected repos).
one could make it an advisory message which can be explictly squelched.