Re: why is git destructive by default? (i suggest it not be!)

From: Nicolas Pitre <nico@cam.org>
Date: Jun 24, 2008, 02:17 UTC
Message-ID: <alpine.LFD.1.10.0806232213360.2979@xanadu.home>
In-Reply-To: <willow-jeske-01l5cKsCFEDjC=91MX@videotron.ca>

On Tue, 24 Jun 2008, David Jeske wrote:

Show 5 quoted lines

> I've heard from a couple users that the solution to these problems is to "go
> dig what you need out of the log, it's still in there". However, it's only in
> there until the log is garbage collected. This either means they are
> destructive operations, or we expect "running without ever collecting the log"
> to be a valid mode of operation... which I doubt is the case.

Why not?

> Question: How about assuring ALL operations can be done non-destructivly by
> default?

	git config --global gc.reflogexpire "2 years"

Nicolas

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.