From: Michael J Gruber <git@drmicha.warpmail.net>
To: Yngve Nysaeter Pettersen <yngve@opera.com>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>, git@vger.kernel.org
Subject: Re: Opera release Git-splitter, a sub-modularizing tool for Git
Date: Sat, 22 Dec 2012 17:41:27 +0100 [thread overview]
Message-ID: <50D5E2B7.5010303@drmicha.warpmail.net> (raw)
In-Reply-To: <op.wpontloxvqd7e2@damia.oslo.osa>
Yngve Nysaeter Pettersen venit, vidit, dixit 21.12.2012 21:13:
> On Fri, 21 Dec 2012 16:49:21 +0100, Matthieu Moy
> <Matthieu.Moy@grenoble-inp.fr> wrote:
>
>> "Yngve Nysaeter Pettersen" <yngve@opera.com> writes:
>>
>>> The split command will create a new repository for all files foo in a
>>> folder (path/foo) and their commit history.
>>>
>>> The replant command reverses that process, re-adding the path prefix
>>> for each file. It may be possible to extend that process into one that
>>> automatically reintegrates the new commits in the original history,
>>> but I never had time to complete that work.
>>>
>>> I did originally add the "replant" functionality into my version of
>>> the git-subtree script, but given the number of commits in the
>>> original repository, git-subtree turned out to be inefficient, due to
>>> the use of temporary files (tens of thousands of files IIRC).
>>>
>>> Those problems led to my development of git-splitter in Python
>>> (bypassing the problem of temporary files), but just including the
>>> functionality I needed, join was not one of those functions.
>>
>> That still doesn't answer the question: why did you need to write a new
>> tool instead of extending git-subtree?
>
> The primary problem with git-subtree was that I ended up with a temporary
> file directory containing 100+K files, which I tracked back to being used
> to manage the commit-to-tree mapping. On Windows, at least, that literally
> slowed down the process to a crawl.
>
>> If one doesn't use "replant", is your tool different from git-subtree?
>
> No, it is not different. However, my tool will use RAM, not diskspace to
> manage information.
That is some valuable input. It can help improve git-subtree for Windows
users, or replace it by something else.
Michael
prev parent reply other threads:[~2012-12-22 16:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 14:51 Opera release Git-splitter, a sub-modularizing tool for Git Yngve N. Pettersen (Developer Opera Software ASA)
2012-12-21 12:23 ` Michael J Gruber
2012-12-21 12:43 ` Yngve Nysaeter Pettersen
2012-12-21 13:49 ` Michael J Gruber
2012-12-21 15:02 ` Yngve Nysaeter Pettersen
2012-12-21 15:49 ` Matthieu Moy
2012-12-21 20:13 ` Yngve Nysaeter Pettersen
2012-12-22 16:41 ` Michael J Gruber [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50D5E2B7.5010303@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=yngve@opera.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).