From: Jeff King <peff@peff.net>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: dealmaker <vinkhc@gmail.com>, git@vger.kernel.org
Subject: Re: How does Git know which files no longer needed during upgrade?
Date: Wed, 4 Mar 2009 04:49:51 -0500 [thread overview]
Message-ID: <20090304094951.GA32433@coredump.intra.peff.net> (raw)
In-Reply-To: <20090303233058.GE4371@genesis.frugalware.org>
On Wed, Mar 04, 2009 at 12:30:58AM +0100, Miklos Vajna wrote:
> First, I think storing upstream code (that you will never touch) in
> version control is a horrible idea, but if you really do it, I would do
> something like:
>
> cd /path/to/copy
> rm -rf *
> cp -a /path/to/new/version/* .
> git add -A
> git commit -m 'update foo to 2.0'
Nit: "rm -rf *" will miss files starting with '.'. So it is probably
simpler to say what you mean: delete all files managed by git:
git ls-files -z | xargs -0 rm -f
-Peff
next prev parent reply other threads:[~2009-03-04 9:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 21:51 How does Git know which files no longer needed during upgrade? dealmaker
2009-03-03 23:30 ` Miklos Vajna
2009-03-04 9:49 ` Jeff King [this message]
2009-03-04 12:28 ` Stefan Näwe
2009-03-04 12:38 ` Jeff King
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=20090304094951.GA32433@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=vinkhc@gmail.com \
--cc=vmiklos@frugalware.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