From: Johannes Sixt <j6t@kdbg.org>
To: Thomas Rast <trast@student.ethz.ch>
Cc: jeffrey.freeman@syncleus.com, git@vger.kernel.org
Subject: Re: [RFC PATCH 0/3] Submodule filtering for filter-branch
Date: Fri, 31 Dec 2010 18:20:13 +0100 [thread overview]
Message-ID: <201012311820.13863.j6t@kdbg.org> (raw)
In-Reply-To: <cover.1293809100.git.trast@student.ethz.ch>
On Freitag, 31. Dezember 2010, Thomas Rast wrote:
> Jeffrey Phillips Freeman aka tty1 asked on IRC about a way to fix the
> super-project after rewriting submodules. This quick series provides
> some extra tricks in the filter-branch toolbox that can be plumbed
> together to achieve this (see the last commit's message), and should
> hopefully be general enough to be of other use too.
I like the --dump-map and --load-map options. But I think that
a --submodule-filter is not necessary; it is just a
particular --index-filter, and IMO should be part of the documentation in the
form of an example that illustrates how to use the new options.
-- Hannes
prev parent reply other threads:[~2010-12-31 17:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-31 15:29 [RFC PATCH 0/3] Submodule filtering for filter-branch Thomas Rast
2010-12-31 15:29 ` [RFC PATCH 1/3] filter-branch: optionally dump all mappings at the end Thomas Rast
2010-12-31 17:09 ` Johannes Sixt
2010-12-31 15:29 ` [RFC PATCH 2/3] filter-branch: optionally load existing mappings prior to filtering Thomas Rast
2010-12-31 17:10 ` Johannes Sixt
2010-12-31 15:29 ` [RFC PATCH 3/3] filter-branch: support --submodule-filter Thomas Rast
2010-12-31 17:31 ` Johannes Sixt
2011-01-03 23:44 ` Jeffrey Phillips Freeman
2011-01-04 13:14 ` Thomas Rast
2011-01-04 19:18 ` Junio C Hamano
2010-12-31 17:20 ` Johannes Sixt [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=201012311820.13863.j6t@kdbg.org \
--to=j6t@kdbg.org \
--cc=git@vger.kernel.org \
--cc=jeffrey.freeman@syncleus.com \
--cc=trast@student.ethz.ch \
/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).