From: Haakon Riiser <haakon.riiser@fys.uio.no>
To: git@vger.kernel.org
Subject: Re: Cleaning the .git directory with gc
Date: Thu, 24 Apr 2008 23:14:58 +0200 [thread overview]
Message-ID: <20080424211458.GA8817@fox> (raw)
In-Reply-To: <20080424005013.GP29771@spearce.org>
[Shawn O. Pearce]
> [...]
> If you _really_ need to whack all of that away, make a clone
> and then discard the old one, e.g.:
>
> git clone file://`pwd`/old_proj new_proj
>
> Note you need to use the file:// URI syntax to prevent Git from
> just hardlinking everything. It takes a little longer, but the
> resulting new_proj will be cruft free.
Thanks for answering my question so quickly. I really wasn't that
worried about it, but seemed strange that the --amend option only
seemed to affect the logs. Anyway, it's nice to know I can start
with a clean slate if I want to by cloning from a file:// path.
--
Haakon
prev parent reply other threads:[~2008-04-24 21:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 23:13 Cleaning the .git directory with gc Haakon Riiser
2008-04-24 0:09 ` Russ Dill
2008-04-24 0:32 ` David Tweed
2008-04-24 0:57 ` Shawn O. Pearce
2008-04-24 0:50 ` Shawn O. Pearce
2008-04-24 21:14 ` Haakon Riiser [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=20080424211458.GA8817@fox \
--to=haakon.riiser@fys.uio.no \
--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).