git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Truncating and cleaning a imported git repositary to make it more usable

From
ABAlex Bennee <kernel-hacker@bennee.com>
Date
Mar 28, 2008, 15:52 UTC
Message-ID
<b2cdc9f30803280852y4f160bb2tda1e688ddf7213e7@mail.gmail.com>
In-Reply-To
<32541b130803280550u2ed23b5auc84bf935d5344e84@mail.gmail.com>
On Fri, Mar 28, 2008 at 12:50 PM, Avery Pennarun <apenwarr@gmail.com> wrote:
Show 15 quoted lines
> On 3/28/08, Alex Bennee <kernel-hacker@bennee.com> wrote:
>  >  2. Create a new repo, starting at the common ancestor point
>  >
>  >   2(a). I'd need to remove the orphaned old CVS modules which are still
>  >  around but not referenced any more.
>  >
>  >  3. Create the product branches and import ANCESTOR..BRANCH_HEAD into
>  >  them
>
>  You probably want to look at git-filter-branch, particularly the
>  --parent-filter option.
>
>  Note that 2(a) would be easiest if you just did it before importing
>  from CVS at all, since it's easy to remove old modules from CVS just
>  by moving the files out of the way.

Ahh, having investigated further it seems the repo contains two CVS modules which account for about 1/3 of the checkout and are not needed (as they are standalone and separate). When I do the final import from CVS I can skip them. Having said that I'll need to run that over the weekend as cvsps takes up so much memory and swaps a lot.

I tried what I think is the correct usage of git-filter-branch but I get:

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?

Any ideas?
-- 
Alex, homepage: http://www.bennee.com/~alex/
Previous: Alex BenneeNext: Alex Bennee
Message 4 of 14 in “Truncating and cleaning a imported git repositary to make it more usable”
  1. Alex BenneeMar 28, 2008
  2. Avery PennarunMar 28, 2008
  3. Alex BenneeMar 28, 2008
  4. Alex BenneeMar 28, 2008
  5. Alex BenneeMar 28, 2008
  6. Johannes SixtMar 28, 2008
  7. Documentation: Another example for git-filter-branchAlex Bennee, Mar 28, 2008
  8. Mike HommeyMar 28, 2008
  9. Alex BenneeMar 29, 2008
  10. Jakub NarebskiMar 29, 2008
  11. Johannes SixtMar 31, 2008
  12. Jeff KingMar 28, 2008
  13. Jeff KingMar 28, 2008
  14. Michael HaggertyMar 29, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.