>> The only potential issue I see is that after the splitting of the >> repository, they will have different commit ids than the original >> repository had. Since the repository is not published that long, I tend >> to think that this is not important. > > That probably won't be much of an issue... Aside from the fact that it > will create a new head when anyone pulls down the new repo (hopefully > that wouldn't confuse any automated package managers, like Arch Linux's > yaourt (there is already a vim-latex-git on AUR)). > > Alternatively, you could keep the htdocs in the history. Clone the > current repo into two, and then (within each clone) move the files to > their desired locations and commit the changes. Of course, you probably > don't need to maintain the changelog within the new "vim-latex-htdocs" > repo, and so that one could be split out regardless.
I think, one could separate both repos with "git filter-branch". For the vimfiles a "--subdirectory-filter vimfiles/" will work and for the remaining part one has to use '--tree-filter "rm -rf vimfiles"'. This split the repo into two and preserves all commit/log entries. Both repos do not know the history of the other one - thus there is no "history overhead". Regards Gerd ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Vim-latex-devel mailing list Vim-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
