From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Johannes Sixt <J.Sixt@eudaptics.com>, git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Teach filter-branch about subdirectory filtering
Date: Fri, 8 Jun 2007 14:03:06 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0706081358060.4059@racer.site> (raw)
In-Reply-To: <46690315.8244CAF7@eudaptics.com>
Hi,
On Fri, 8 Jun 2007, Johannes Sixt wrote:
> Johannes Schindelin wrote:
> > It's just a guess, but now that we come really, really close to having
> > a concise implementation of git-subproject which will probably soon
> > propagate to master, and then maint, I gather that more and more
> > people come and want to split their projects (which they maintained as
> > one big project) into several subprojects (which they should have been
> > from the start, but the tool did not easily allow for that).
>
> I think that --subdirectry-filter needs to become a bit smarter to be
> really useful for splitting a big project into sub-projects plus a
> super-project. The reason is that once you have extracted the
> sub-project(s), you have a hard time to find out which commits to
> gitlink into the super-project. I don't have a plan how to make it
> smarter, though.
Yes, it seems a good direction to follow.
I will have to think about it, but I guess that with yet another set of
files in ../map/ (probably prefixed by the subdirectory name), we should
even be able to smartly filter a huge project into a super-project
together with its subprojects.
The command line option would be something like "--split-superproject
dir1,dir2,dir3", where dir<n> are the subdirectories that are to become
the subprojects.
Ciao,
Dscho
next prev parent reply other threads:[~2007-06-08 13:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 0:30 [PATCH] Teach filter-branch about subdirectory filtering Johannes Schindelin
2007-06-08 0:57 ` Junio C Hamano
2007-06-08 5:04 ` Johannes Schindelin
2007-06-08 7:19 ` Johannes Sixt
2007-06-08 13:03 ` Johannes Schindelin [this message]
2007-06-08 13:19 ` Johannes Sixt
2007-06-08 21:05 ` Alex Riesen
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.0706081358060.4059@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=J.Sixt@eudaptics.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).