From: Petr Baudis <pasky@suse.cz>
To: jamal <hadi@cyberus.ca>
Cc: git@vger.kernel.org
Subject: Re: cg-rm suggestion
Date: Wed, 21 Sep 2005 16:15:52 +0200 [thread overview]
Message-ID: <20050921141552.GC17981@pasky.or.cz> (raw)
In-Reply-To: <1126531426.6380.2.camel@localhost.localdomain>
Dear diary, on Mon, Sep 12, 2005 at 03:23:46PM CEST, I got a letter
where jamal <hadi@cyberus.ca> told me that...
> Folks,
>
> I am not on the list so cc if you respond.
>
> A small suggestion for cg-rm: Can you make the default not to physically
> remove the file since that is more destructive?
> Unless there is a way to recover it.
>
> Let someone who wants to delete explicitly specify it. Or maybe even do
> the rm -i like option of prompting.
Yes, it was changed to only cg-rm -f physically removing the file.
Thanks for the suggestion.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
prev parent reply other threads:[~2005-09-21 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 13:23 cg-rm suggestion jamal
2005-09-21 14:15 ` Petr Baudis [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050921141552.GC17981@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=hadi@cyberus.ca \
/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 NNTP newsgroup(s).