From: Anand Kumria <wildfire@progsoc.org>
To: git@vger.kernel.org
Subject: Re: [PATCH] Removed the printf("rm 'file'") from git-rm.
Date: Sun, 25 Mar 2007 16:38:59 +0000 (UTC) [thread overview]
Message-ID: <pan.2007.03.25.16.39.10@progsoc.org> (raw)
In-Reply-To: 7vodmhc06f.fsf@assigned-by-dhcp.cox.net
On Sat, 24 Mar 2007 23:22:16 -0700, Junio C Hamano wrote:
> Tilman Sauerbeck <tilman@code-monkey.de> writes:
>
>> We used to print that, because you actually had to run the output of
>> git-rm to get rid of the files before Git 1.5. Now that git-rm really
>> removes the files, it's not needed anymore.
>
> Even though I admit I do not deeply care, as I never use 'git rm'
> myself, I do not necessarily agree with "because" part.
>
> I suspect people are by now accustomed to see the assuring feedback from
> the command when used this way:
>
> $ git rm -r one
> rm 'one/1'
> rm 'one/2'
> rm 'one/3'
Heh. I didn't even know there was a recursive option. So I'm definitely
not 'accustomed' to any form of output.
If me being a data point helps at all.
Anand
next prev parent reply other threads:[~2007-03-25 16:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11747590062554-git-send-email-tilman@code-monkey.de>
2007-03-25 6:22 ` [PATCH] Removed the printf("rm 'file'") from git-rm Junio C Hamano
2007-03-25 16:38 ` Anand Kumria [this message]
2007-03-25 21:04 ` Tilman Sauerbeck
2007-03-25 21:36 ` Johannes Schindelin
2007-03-26 10:28 ` [PATCH] git-rm: add --quiet option to suppress "rm 'file'" messages Eric Lesh
2007-03-26 22:56 ` Junio C Hamano
2007-03-26 22:13 ` [PATCH] Removed the printf("rm 'file'") from git-rm Martin Waitz
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=pan.2007.03.25.16.39.10@progsoc.org \
--to=wildfire@progsoc.org \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.