From: LitHack <lithack0@gmail.com>
To: 64326@debbugs.gnu.org
Subject: bug#64326: Bug in rm command
Date: Wed, 28 Jun 2023 18:05:17 +0530 [thread overview]
Message-ID: <CADc_fS2aMmVHvDTqU29RfC1uJFHcG6YARjt3QyM9T0X7oq3cZg@mail.gmail.com> (raw)
There is bug in rm command by which we can not delete a special file with
dash(-) in front of them.
Like rm -file, rm "-file" will not delete the file (-file)
next reply other threads:[~2023-06-28 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 12:35 LitHack [this message]
2023-06-28 15:02 ` bug#64326: Some more info about rm bug LitHack
2023-06-28 15:41 ` Arsen Arsenović via GNU coreutils Bug Reports
[not found] ` <5f118d81-987f-df2e-dc4f-0b53a7ae886d@gmail.com>
2023-06-28 21:02 ` Bernhard Voelker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-coreutils
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADc_fS2aMmVHvDTqU29RfC1uJFHcG6YARjt3QyM9T0X7oq3cZg@mail.gmail.com \
--to=lithack0@gmail.com \
--cc=64326@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).