From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Mike Hommey <mh@glandium.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git-filter-branch
Date: Thu, 9 Aug 2007 10:38:09 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708091037220.21857@racer.site> (raw)
In-Reply-To: <20070809093051.GA21458@glandium.org>
Hi,
On Thu, 9 Aug 2007, Mike Hommey wrote:
> On Thu, Aug 09, 2007 at 10:19:20AM +0100, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > > In the description in the manpage:
> > > Lets you rewrite git revision history by creating a new branch from
> > > your current branch, applying custom filters on each revision.
> > > (...)
> > > The command takes the new branch name as a mandatory argument and the
> > > filters as optional arguments
> > >
> > > And in example:
> > > Now, you will get the rewritten history saved in the branch newbranch
> > > (your current branch is left untouched).
> > >
> > > I must say this is a feature that would actually be nice to have...
> >
> > To compare with the old one? Use reflogs:
> >
> > git filter-branch --some-option master
> > git diff master@{1}..master
>
> To have, for example, a branch tracking an upstream (svn or whatever)
> repository and have a branch based on it, only differing in the fact that
> some directories get removed.
You can always achieve the same effect by
$ git branch new-branch master
$ git filter-branch <options> master
Anyway, I'm off for a few days.
Ciao,
Dscho
prev parent reply other threads:[~2007-08-09 9:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 6:34 git-filter-branch Mike Hommey
2007-08-09 8:58 ` git-filter-branch Johannes Schindelin
2007-08-09 9:15 ` git-filter-branch Mike Hommey
2007-08-09 9:19 ` git-filter-branch Johannes Schindelin
2007-08-09 9:30 ` git-filter-branch Mike Hommey
2007-08-09 9:38 ` 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.0708091037220.21857@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=mh@glandium.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).