From: Jeff King <peff@peff.net>
To: Alex Bennee <kernel-hacker@bennee.com>
Cc: Avery Pennarun <apenwarr@gmail.com>, git@vger.kernel.org
Subject: Re: Truncating and cleaning a imported git repositary to make it more usable
Date: Fri, 28 Mar 2008 14:08:49 -0400 [thread overview]
Message-ID: <20080328180848.GA8299@coredump.intra.peff.net> (raw)
In-Reply-To: <b2cdc9f30803280903w4a6e3a6l9e33fd188af9995a@mail.gmail.com>
On Fri, Mar 28, 2008 at 04:03:18PM +0000, Alex Bennee wrote:
> > ajb@pitcairn:/export/git/fresh.git$ git-filter-branch --tree-filter
> > 'rm -rf big_dira big_dirb' dev-branch
> > warning: refname 'dev-branch' is ambiguous.
> > Which ref do you want to rewrite?
You have two refs called dev-branch. Probably both a tag and a branch
(i.e., refs/heads/dev-branch and refs/tags/dev-branch). You can
disambiguate by saying "heads/dev-branch").
> Ignore me. Not sure why but:
>
> git-checkout dev-branch
> git-filter-branch --tree-filter 'rm -rf big_dira big_dirb' HEAD
git-checkout prefers branches to tags[1], so there is no ambiguity. It
puts the full refname (refs/heads/dev-branch) into your HEAD, so there
is no ambiguity when saying "HEAD".
[1] Actually, the upcoming builtin-checkout no longer behaves this way,
and will complain about the ambiguity.
-Peff
next prev parent reply other threads:[~2008-03-28 18:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 12:35 Truncating and cleaning a imported git repositary to make it more usable Alex Bennee
2008-03-28 12:50 ` Avery Pennarun
2008-03-28 13:08 ` Alex Bennee
2008-03-28 15:52 ` Alex Bennee
2008-03-28 16:03 ` Alex Bennee
2008-03-28 16:43 ` Johannes Sixt
2008-03-28 18:07 ` [PATCH] Documentation: Another example for git-filter-branch Alex Bennee
2008-03-28 20:44 ` Truncating and cleaning a imported git repositary to make it more usable Mike Hommey
2008-03-29 13:47 ` Alex Bennee
2008-03-29 14:30 ` Jakub Narebski
2008-03-31 6:17 ` Johannes Sixt
2008-03-28 18:08 ` Jeff King [this message]
2008-03-28 18:19 ` Jeff King
2008-03-29 17:51 ` Michael Haggerty
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=20080328180848.GA8299@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=kernel-hacker@bennee.com \
/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).