git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <J.Sixt@eudaptics.com>
To: git@vger.kernel.org
Subject: Re: efficient way to filter several branches with common history?
Date: Wed, 04 Jul 2007 10:37:31 +0200	[thread overview]
Message-ID: <468B5C4B.26F5E90B@eudaptics.com> (raw)
In-Reply-To: 652B0F85-D0E4-4BF0-8DFC-212B6C0650AF@zib.de

Steffen Prohaska wrote:
> 
> Is there an efficient way to filter several branches at once
> through git-filter-branch? Often several branches have a lot
> of common history. Therefore, I suspect it would be much more
> efficient to filter them with one call to git-filter-branch.
> For example how can I efficiently filter all origin/* branches
> to filtered/* branches?

That feature is not yet implemented.

In the meantime do it this way:

Make an octopus merge of the branches onto a new branch. (If you have
more than a dozen or so, you better make a hierarchy of octopusses.) You
don't need to resolve conflicts (you are not interested in the merge
result), or use -s ours to avoid them in the first place.
Then filter that new branch.
Then create new refs at the rewritten commits:

   $ git update-ref refs/filtered/b1 $id-of-rewritten-origin/b1
   $ ...

Use gitk to find the $ids-of-rewritten-origin/*

-- Hannes

  reply	other threads:[~2007-07-04  8:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-04  8:11 efficient way to filter several branches with common history? Steffen Prohaska
2007-07-04  8:37 ` Johannes Sixt [this message]
2007-07-04 13:27   ` Steffen Prohaska
2007-07-04 14:28     ` Johannes Schindelin

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=468B5C4B.26F5E90B@eudaptics.com \
    --to=j.sixt@eudaptics.com \
    --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).