git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: No Checkout / Read Only config Flag

From
Philip Oakley <philipoakley@iee.email>
Date
Nov 8, 2019, 16:08 UTC
Message-ID
<baf800ba-d92c-74be-d590-56f3bb4c6c44@iee.email>
In-Reply-To
<f3378b7b-c745-58db-55ed-c2c2a6818734@gmx.de>
On 07/11/2019 21:34, Ingo Wolf wrote:
> Hi,
>
> is there a readonly / no checkout flag in the git configs?
>

Not that I'm aware of, but the use-case isn't clear, and is perhaps contrary to actually having a version management system

> I use Git to trace / Backup some worktrees and would like to prevent
> changing them accidentally with git.
>

How would such 'accidents' happen? What's the size of the worktree and how do you do such an accidental commit?

I could see that if you are changing hundreds of files within a commit, and only one or two files need preserved, then did a `git add -A` you would include any changes to those one or two special files, which needed special attention.

This feels similar but not quite the same as previous discussions about 'precious' files (the latter commonly being untracked/ignored, but shouldn't be removed/cleaned).

Technology won't solve the human error modes..., though a clear use case can help.

-- 
Philip
Previous: Ingo WolfNext: Konstantin Khomoutov
Message 2 of 3 in “No Checkout / Read Only config Flag”
  1. Ingo WolfNov 7, 2019
  2. Philip OakleyNov 8, 2019
  3. Konstantin KhomoutovNov 8, 2019

Read the whole thread, see it on lore, or plain text.

$ 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.