From: Pazu <pazu@pazu.com.br>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: git-rm'ing all dead files
Date: Wed, 24 Jan 2007 15:02:07 -0200 [thread overview]
Message-ID: <9e7ab7380701240902i4168cc40x1629e76bdf75dcfb@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0701241756300.22628@wbgn013.biozentrum.uni-wuerzburg.de>
2007/1/24, Johannes Schindelin <Johannes.Schindelin@gmx.de>:
> You _can_ use
>
> git ls-files -z -d | xargs -0 git rm --cached
>
> So, you did not find that option with git-rm, because it is an option to
> xargs...
I remember trying that, but git-rm was still confused about spaces in
filenames. I'll try it again the next time I'm in a situation like
that.
-- Pazu
prev parent reply other threads:[~2007-01-24 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 16:17 git-rm'ing all dead files Pazu
2007-01-24 16:25 ` Johannes Schindelin
2007-01-24 16:51 ` Pazu
2007-01-24 16:57 ` Johannes Schindelin
2007-01-24 17:02 ` Pazu [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=9e7ab7380701240902i4168cc40x1629e76bdf75dcfb@mail.gmail.com \
--to=pazu@pazu.com.br \
--cc=Johannes.Schindelin@gmx.de \
--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 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).