From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Steffen Prohaska <prohaska@zib.de>
Cc: Johannes Sixt <J.Sixt@eudaptics.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: efficient way to filter several branches with common history?
Date: Wed, 4 Jul 2007 15:28:15 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707041527050.4071@racer.site> (raw)
In-Reply-To: <6DC0E50A-CAD3-453E-BD9C-73E51EDD5785@zib.de>
Hi,
On Wed, 4 Jul 2007, Steffen Prohaska wrote:
> On Jul 4, 2007, at 10:37 AM, Johannes Sixt wrote:
>
> > Steffen Prohaska wrote:
> > >
> > > Is there an efficient way to filter several branches at once
> > > through git-filter-branch?
> >
> > That feature is not yet implemented.
> >
> > In the meantime do it this way:
> >
> > [...]
>
> Thanks for your explanation. The following is the template I used
> to build my fully automated version of what you proposed:
>
> [...]
Since you seem quite proficient in shell, why not implement this feature
in filter-branch (which is a shell script) to begin with?
Ciao,
Dscho
prev parent reply other threads:[~2007-07-04 14:28 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
2007-07-04 13:27 ` Steffen Prohaska
2007-07-04 14:28 ` Johannes Schindelin [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=Pine.LNX.4.64.0707041527050.4071@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=J.Sixt@eudaptics.com \
--cc=git@vger.kernel.org \
--cc=prohaska@zib.de \
/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).