# Opera release Git-splitter, a sub-modularizing tool for Git 8 messages from 2012-12-18 to 2012-12-22. Participants: Yngve N. Pettersen (Developer Opera Software ASA), Michael J Gruber, Yngve Nysaeter Pettersen, Matthieu Moy. Thread: https://gitlist.dev/t/32383 ## Yngve N. Pettersen (Developer Opera Software ASA), 2012-12-18 14:51 Subject: Opera release Git-splitter, a sub-modularizing tool for Git Message-ID: URL: https://gitlist.dev/e/op.wpiovoj5qrq7tp%40acorna.invalid.invalid ``` Hello all, Today Opera Software released the "Git-splitter", a small tool for sub-modularizing code in a git repo, with complete commit history, under the Apache 2.0 license. It's functionality is similar to "git-subtree", but also include a command for reversing the process. The code is hosted on GitHub: We have announced the release as part of another announcement of released code at the Opera Security Group home page: -- Sincerely, Yngve N. Pettersen ******************************************************************** Senior Developer Email: yngve@opera.com Opera Software ASA http://www.opera.com/ Phone: +47 96 90 41 51 Fax: +47 23 69 24 01 ******************************************************************** ``` ## Michael J Gruber, 2012-12-21 12:23 Subject: Re: Opera release Git-splitter, a sub-modularizing tool for Git Message-ID: <50D454D2.5030403@drmicha.warpmail.net> URL: https://gitlist.dev/e/50D454D2.5030403%40drmicha.warpmail.net In-Reply-To: ``` Yngve N. Pettersen (Developer Opera Software ASA) venit, vidit, dixit 18.12.2012 15:51: > Hello all, > > Today Opera Software released the "Git-splitter", a small tool for > sub-modularizing code in a git repo, with complete commit history, under > the Apache 2.0 license. > > It's functionality is similar to "git-subtree", but also include a command > for reversing the process. Is there something keeping you technically from adding a join command to git-subtree? > The code is hosted on GitHub: > > > We have announced the release as part of another announcement of released > code at the Opera Security Group home page: > > ``` ## Yngve Nysaeter Pettersen, 2012-12-21 12:43 Subject: Re: Opera release Git-splitter, a sub-modularizing tool for Git Message-ID: URL: https://gitlist.dev/e/op.wpn2xz07vqd7e2%40damia.oslo.osa In-Reply-To: <50D454D2.5030403@drmicha.warpmail.net> ``` Hi, On Fri, 21 Dec 2012 13:23:46 +0100, Michael J Gruber wrote: > Yngve N. Pettersen (Developer Opera Software ASA) venit, vidit, dixit > 18.12.2012 15:51: >> Hello all, >> >> Today Opera Software released the "Git-splitter", a small tool for >> sub-modularizing code in a git repo, with complete commit history, under >> the Apache 2.0 license. >> >> It's functionality is similar to "git-subtree", but also include a >> command >> for reversing the process. > > Is there something keeping you technically from adding a join command to > git-subtree? Probably not, but within the process I was working I did not want to merge the branch with the recreated history for that path into the existing codebase (I don't like duplicate histories) so I used rebasing to move the new commits over, instead, and therefore did not need a join command. Feel free to add a join command, if you want one. >> The code is hosted on GitHub: >> >> >> We have announced the release as part of another announcement of >> released >> code at the Opera Security Group home page: >> >> -- Sincerely, Yngve N. Pettersen ******************************************************************** Senior Developer Email: yngve@opera.com Opera Software ASA http://www.opera.com/ Phone: +47 96 90 41 51 Fax: +47 23 69 24 01 ******************************************************************** ``` ## Michael J Gruber, 2012-12-21 13:49 Subject: Re: Opera release Git-splitter, a sub-modularizing tool for Git Message-ID: <50D468E6.2090900@drmicha.warpmail.net> URL: https://gitlist.dev/e/50D468E6.2090900%40drmicha.warpmail.net In-Reply-To: ``` Yngve Nysaeter Pettersen venit, vidit, dixit 21.12.2012 13:43: > Hi, > > On Fri, 21 Dec 2012 13:23:46 +0100, Michael J Gruber > wrote: > >> Yngve N. Pettersen (Developer Opera Software ASA) venit, vidit, dixit >> 18.12.2012 15:51: >>> Hello all, >>> >>> Today Opera Software released the "Git-splitter", a small tool for >>> sub-modularizing code in a git repo, with complete commit history, under >>> the Apache 2.0 license. >>> >>> It's functionality is similar to "git-subtree", but also include a >>> command >>> for reversing the process. >> >> Is there something keeping you technically from adding a join command to >> git-subtree? > > Probably not, but within the process I was working I did not want to merge > the branch with the recreated history for that path into the existing > codebase (I don't like duplicate histories) so I used rebasing to move the > new commits over, instead, and therefore did not need a join command. > > Feel free to add a join command, if you want one. Im sorry, but that was a total misunderstanding. You said git-splitter is like git-subtree but adds a command for reversing the process. My question was: What kept you from adding that to git-subtree (rather than redoing stiff that git-subtree does)? I just assumed that reversing the process of splitting must be joining. It may very well be that git-splitter does things differently, i.e. that there are more differences than just added functionality (compared to git-subtree), but that is not clear from the announcement. >>> The code is hosted on GitHub: >>> >>> >>> We have announced the release as part of another announcement of >>> released >>> code at the Opera Security Group home page: >>> >>> > > ``` ## Yngve Nysaeter Pettersen, 2012-12-21 15:02 Subject: Re: Opera release Git-splitter, a sub-modularizing tool for Git Message-ID: URL: https://gitlist.dev/e/op.wpn9d6xuvqd7e2%40damia.oslo.osa In-Reply-To: <50D468E6.2090900@drmicha.warpmail.net> ``` On Fri, 21 Dec 2012 14:49:26 +0100, Michael J Gruber wrote: > Yngve Nysaeter Pettersen venit, vidit, dixit 21.12.2012 13:43: >> Hi, >> >> On Fri, 21 Dec 2012 13:23:46 +0100, Michael J Gruber >> wrote: >> >>> Yngve N. Pettersen (Developer Opera Software ASA) venit, vidit, dixit >>> 18.12.2012 15:51: >>>> Hello all, >>>> >>>> Today Opera Software released the "Git-splitter", a small tool for >>>> sub-modularizing code in a git repo, with complete commit history, >>>> under >>>> the Apache 2.0 license. >>>> >>>> It's functionality is similar to "git-subtree", but also include a >>>> command >>>> for reversing the process. >>> >>> Is there something keeping you technically from adding a join command >>> to >>> git-subtree? >> >> Probably not, but within the process I was working I did not want to >> merge >> the branch with the recreated history for that path into the existing >> codebase (I don't like duplicate histories) so I used rebasing to move >> the >> new commits over, instead, and therefore did not need a join command. >> >> Feel free to add a join command, if you want one. > > Im sorry, but that was a total misunderstanding. You said git-splitter > is like git-subtree but adds a command for reversing the process. My > question was: What kept you from adding that to git-subtree (rather than > redoing stiff that git-subtree does)? > > I just assumed that reversing the process of splitting must be joining. > > It may very well be that git-splitter does things differently, i.e. that > there are more differences than just added functionality (compared to > git-subtree), but that is not clear from the announcement. 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. >>>> The code is hosted on GitHub: >>>> >>>> >>>> We have announced the release as part of another announcement of >>>> released >>>> code at the Opera Security Group home page: >>>> >>>> >> >> -- Sincerely, Yngve N. Pettersen ******************************************************************** Senior Developer Email: yngve@opera.com Opera Software ASA http://www.opera.com/ Phone: +47 96 90 41 51 Fax: +47 23 69 24 01 ******************************************************************** ``` ## Matthieu Moy, 2012-12-21 15:49 Subject: Re: Opera release Git-splitter, a sub-modularizing tool for Git Message-ID: URL: https://gitlist.dev/e/vpqhanf2yny.fsf%40grenoble-inp.fr In-Reply-To: ``` "Yngve Nysaeter Pettersen" 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? If one doesn't use "replant", is your tool different from git-subtree? -- Matthieu Moy http://www-verimag.imag.fr/~moy/ ``` ## Yngve Nysaeter Pettersen, 2012-12-21 20:13 Subject: Re: Opera release Git-splitter, a sub-modularizing tool for Git Message-ID: URL: https://gitlist.dev/e/op.wpontloxvqd7e2%40damia.oslo.osa In-Reply-To: ``` On Fri, 21 Dec 2012 16:49:21 +0100, Matthieu Moy wrote: > "Yngve Nysaeter Pettersen" 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. -- Sincerely, Yngve N. Pettersen ******************************************************************** Senior Developer Email: yngve@opera.com Opera Software ASA http://www.opera.com/ Phone: +47 96 90 41 51 Fax: +47 23 69 24 01 ******************************************************************** ``` ## Michael J Gruber, 2012-12-22 16:41 Subject: Re: Opera release Git-splitter, a sub-modularizing tool for Git Message-ID: <50D5E2B7.5010303@drmicha.warpmail.net> URL: https://gitlist.dev/e/50D5E2B7.5010303%40drmicha.warpmail.net In-Reply-To: ``` Yngve Nysaeter Pettersen venit, vidit, dixit 21.12.2012 21:13: > On Fri, 21 Dec 2012 16:49:21 +0100, Matthieu Moy > wrote: > >> "Yngve Nysaeter Pettersen" 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 ```