Linux

47233 readers

773 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Can I remove a git repo without resorting to rm -rf ? (programming.dev)

submitted 3 months ago by Buttons@programming.dev to c/linux@lemmy.ml

7 comments fedilink hide all child comments

Git repos have lots of write protected files in the .git directory, sometimes hundreds, and the default rm my_project_managed_by_git will prompt before deleting each write protected file. So, to actually delete my project I have to do rm -rf my_project_managed_by_git.

Using rm -rf scares me. Is there a reasonable way to delete git repos without it?

top 7 comments

sorted by: hot top controversial new old

[–] nottelling@lemmy.world 0 points 3 months ago (1 children)

So.... you're afraid of the command that does the thing you're trying to do?

[–] Buttons@programming.dev 0 points 3 months ago* (last edited 3 months ago) (1 children)

More like, I'm afraid of the command doing more than I'm trying to do.

What I want to do is ignore prompts about write-protected files in the .git directory, what it does is ignore all prompts for all files.

[–] saigot@lemmy.ca 0 points 3 months ago (1 children)

so why not rm -rf folder/.git/* then rm -r folder/*

[–] fhein@lemmy.world 0 points 3 months ago (1 children)

Maybe they're afraid of accidentally writing rm -rf folder/.git /* or something

[–] Buttons@programming.dev 1 points 3 months ago

That's a good example. If I'm regularly running a command that is a single whitespace character away from disaster, that's a problem.

Imagine a fighter aircraft that had an eject button on the side of the flight stick. The pilot complains "I'm afraid I might accidentally hit the eject button when I don't need to", but everyone responds "why would you push the eject button if you don't want to eject?", or "so your concern is that the eject button will cause you to eject...?" -- That's how I feel right now.

[–] Kekin@lemy.lol 0 points 3 months ago* (last edited 3 months ago) (1 children)

A tip I saw some time ago is to do:

rm folder -rf

Additionally you could move the git folder to the trash folder. I think it's usually located at $HOME/.local/share/trash/files/

Then you can delete it from the trash once you're certain you got the right folder

[–] d_k_bo@feddit.de 0 points 3 months ago* (last edited 3 months ago)

Additionally you could move the git folder to the trash folder. I think it's usually located at $HOME/.local/share/trash/files/

Moving something to the trash files folder isn't the correct way to trash it, since the Trash specification requires storing some metadata for each trash item.

You should use eg. trash-cli instead.