From: Dave Jones <davej@redhat.com>
To: git@vger.kernel.org
Subject: Fwd: Re: git checkout -f branch doesn't remove extra files
Date: Sat, 13 Aug 2005 00:17:37 -0400 [thread overview]
Message-ID: <20050813041737.GB25236@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 65 bytes --]
Gar, got caught by the 'reply-to' going to Tony only...
Dave
[-- Attachment #2: Type: message/rfc822, Size: 1308 bytes --]
From: Dave Jones <davej@redhat.com>
To: "Luck, Tony" <tony.luck@intel.com>
Subject: Re: git checkout -f branch doesn't remove extra files
Date: Sat, 13 Aug 2005 00:16:13 -0400
Message-ID: <20050813041613.GA25236@redhat.com>
On Fri, Aug 12, 2005 at 10:31:17AM -0700, Luck, Tony wrote:
> I've just got around to noticing some of the new (to
> me) features in git, and started experimenting with
> branches.
Seems a good day to learn new features, I was completely
unaware of git-ls-files somehow.
My git snapshot creator that builds the hourly tarballs at
http://www.codemonkey.org.uk/projects/git-snapshots/
currently does an rsync, and then a checkout, and finally
it cleans up by removing all the checked out files.
It currently does this by hand, but on learning about
this 'new' command, I thought, cool, now I can do..
git-ls-files | xargs rm -rf
however, this then leaves a bunch of empty subdirs, as
git-ls-files doesn't list the subdirs by themselves in
the output. Am I missing some other option ?
Dave
next reply other threads:[~2005-08-13 4:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-13 4:17 Dave Jones [this message]
2005-08-13 5:05 ` Fwd: Re: git checkout -f branch doesn't remove extra files Linus Torvalds
2005-08-13 5:27 ` Dave Jones
2005-08-13 5:39 ` Linus Torvalds
2005-08-13 5:33 ` Linus Torvalds
2005-08-13 11:00 ` Petr Baudis
2005-08-13 12:10 ` Sergey Vlasov
2005-08-13 12:33 ` Petr Baudis
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=20050813041737.GB25236@redhat.com \
--to=davej@redhat.com \
--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).