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

Re: [Feature Request] Option to make .git not read-only in cloned repos

From
Johannes Sixt <j6t@kdbg.org>
Date
Aug 25, 2019, 17:54 UTC
Message-ID
<d31b871a-5c2d-99e7-5616-6f43759bb948@kdbg.org>
In-Reply-To
<CAAQViEsZW4PzHr5BrkDHU2kSd_e04n02McGPgrmXGZMpgaTePg@mail.gmail.com>
Am 23.08.19 um 22:43 schrieb Albert Vaca Cintora:
> However, I'm sure that a large percentage of developers out there will
> agree with me that having to use force (-f) to delete every cloned
> repo is annoying, and even worse, it creates the bad habit of always
> force-deleting everything.

IMO, the bad habit is to delete cloned repositories all the time. If your workflow necessitates this, then you are doing something wrong. Maybe you have an X-Y-problem?

-- Hannes
Previous: Albert Vaca CintoraNext: Albert Vaca Cintora
Message 4 of 18 in “[Feature Request] Option to make .git not read-only in cloned repos”
  1. Albert Vaca CintoraAug 23, 2019
  2. Kevin DaudtAug 25, 2019
  3. Albert Vaca CintoraAug 25, 2019
  4. Johannes SixtAug 25, 2019
  5. Albert Vaca CintoraAug 25, 2019
  6. Philip OakleyAug 25, 2019
  7. Junio C HamanoAug 26, 2019
  8. Albert Vaca CintoraAug 26, 2019
  9. SZEDER GáborAug 26, 2019
  10. Junio C HamanoAug 27, 2019
  11. Albert Vaca CintoraAug 30, 2019
  12. Junio C HamanoAug 30, 2019
  13. Michal SuchánekAug 30, 2019
  14. Junio C HamanoAug 30, 2019
  15. Albert Vaca CintoraAug 31, 2019
  16. Randall S. BeckerAug 26, 2019
  17. Junio C HamanoAug 26, 2019
  18. Randall S. BeckerAug 26, 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.