All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.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 17:43:58 +0100	[thread overview]
Message-ID: <47ED204E.3020602@viscovery.net> (raw)
In-Reply-To: <b2cdc9f30803280903w4a6e3a6l9e33fd188af9995a@mail.gmail.com>

Alex Bennee schrieb:
> On Fri, Mar 28, 2008 at 3:52 PM, Alex Bennee <kernel-hacker@bennee.com> 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?
> 
> Ignore me. Not sure why but:
> 
> git-checkout dev-branch
> git-filter-branch --tree-filter  'rm -rf big_dira big_dirb' HEAD

You really shouldn't do it this way, unless you do it on a ramdisk. Better
use an --index-filter. This is modeled after the last example in the man
page (and, of course, untested):

git filter-branch --index-filter \
        'git ls-files -s |
	 grep -v "	big_dira" |
	 grep -v "	big_dirb" |
                GIT_INDEX_FILE=$GIT_INDEX_FILE.new \
                        git update-index --index-info &&
         mv $GIT_INDEX_FILE.new $GIT_INDEX_FILE' HEAD

where the space before big_dir is actually a literal TAB!

-- Hannes

  reply	other threads:[~2008-03-28 16:45 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 [this message]
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
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=47ED204E.3020602@viscovery.net \
    --to=j.sixt@viscovery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.