From: greened@obbligato.org (David A. Greene)
To: Marcus Brinkmann <m.brinkmann@semantics.de>
Cc: Junio C Hamano <gitster@pobox.com>,
Dave Ware <davidw@realtimegenomics.com>, <git@vger.kernel.org>
Subject: Re: [PATCH] contrib/subtree: Split history with empty trees correctly
Date: Wed, 27 Jan 2016 20:56:47 -0600 [thread overview]
Message-ID: <87fuxil8cw.fsf@waller.obbligato.org> (raw)
In-Reply-To: <56A4CC85.90705@semantics.de> (Marcus Brinkmann's message of "Sun, 24 Jan 2016 14:07:17 +0100")
Marcus Brinkmann <m.brinkmann@semantics.de> writes:
> With my patch, "git subtree split -P" produces the same result (for my
> data set) as "git filter-branch --subdirectory-filter", which is much
> faster, because it selects the revisions to rewrite before rewriting.
> As I am not using any of the advanced features of "git subtree", I will
> just use "git filter-branch" instead.
Heh. :)
I hope to replace all that ugly split code with filter-branch as you
describe but there are some cases where it differs. It may be that your
changes fix some of that.
Are you still able to do a re-roll on this?
-David
next prev parent reply other threads:[~2016-01-28 2:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 16:23 BUG: git subtree split gets confused on removed and readded directory Marcus Brinkmann
2016-01-15 23:44 ` Junio C Hamano
2016-01-17 19:34 ` David Ware
2016-01-17 23:23 ` David A. Greene
2016-01-20 1:17 ` [PATCH] contrib/subtree: Split history with empty trees correctly (was: Re: BUG: git subtree split gets confused on removed and readded directory) Marcus Brinkmann
2016-01-20 4:05 ` [PATCH] contrib/subtree: Split history with empty trees correctly David A. Greene
2016-01-20 11:22 ` Marcus Brinkmann
2016-01-28 2:55 ` David A. Greene
2016-01-24 13:07 ` Marcus Brinkmann
2016-01-28 2:56 ` David A. Greene [this message]
2016-01-28 4:06 ` Marcus Brinkmann
2016-02-03 2:34 ` David A. Greene
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=87fuxil8cw.fsf@waller.obbligato.org \
--to=greened@obbligato.org \
--cc=davidw@realtimegenomics.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=m.brinkmann@semantics.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 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.