4/9/2024 0 Comments Kink checklist git![]() The overall run-time of the conversion has been measure to about 30 minutes. The main such proposed clean-up is the tab/space clean-up (eliminate tabs in sources) and the trailing spaces clean-up.Ī custom C program, sandwiched between git fast-export and git fast-import, allow to do that clean-up very efficiently. Since the migration will result in a discontinuity of ours repositories, it might be a good time to sneak in intrusive clean-up that require a complete rewrite of the history. Translations is left untouched and will still be optionally present as Sens that it is not required to build the product. The translations repository is a big repository, managed quasi-exclusively by tar.gz files, the tags will be renamed and the result combined with core. The remaining libs-extern-sys will undergo a git-filter to remove historical. The dictionaries module will be extracted from libs-extern-sys and spined-off as a separate repository. Libs-extern-sys as it stand is a pretty big repository, in fact our biggestīut without dictionaries and with a clean-up of the old historical That module is fairly independent of the mainline development. The case of libs-extern-sys is very similar to that of libs-extern with the added twist that a big part of this repository is used by the 'dictionaries' module. Libs-extern will undergo a git-filter to remove historical */download/* Once again, since we are going to an intrusive reorganization we may as well take advantage of this to do some clean-up and put that repository on a diet. We do not do that anymore, but the history still reflect that. Were dumped into the libs-extern repository. Is due to the fact that once upon a time the tar.gz of these external libraries It is a fairly big repository, but in fact a substantial part of the size Libs-extern is essentially a wrapper to patch and build external libraries. With the added benefit of being completely optional. Managed the same way auxiliary git repositories are managed today The new binfilter git repository will be placed in clone/binfilter and Will have it's tag renamed and combined with core. This save about 60% of the size of filters. Of the git repositories to extract the binfilter module out of the filters repository Take advantage of this intrusive reorganization Since binfilter is deprecated and will eventually be dropped, we will Make that repository even more independent.įilters particularity is being the host of the binfilter module. Today it does depend on libs-gui, for instance, to be build. Technically this is an optional repository, and mostly managed by the documentation and translation team. This repository contains scripts, metadata and data needed to generate the help files. The size of the repository is moderate (with respect to the other repositories)įor simplicity sake, it would be not to costly to consolidate artwork into core. The rate of change is fairly low (46 commits since the beginning of the year ) The graphic design team, and from the dev side change consist mostly into The current version of the onegit.sh script combine all these repositories inĪrtwork contains mostly binary objects. The only processing step is to rename the tag to avoid name-conflict. The will be merged into the new 'core' repository. These are bread-and-butter code repository. ![]() it is left as isĪnd become, after all processing our new 'core' repositoryīase calc components extensions extras impress libs-core libs-gui postprocess sdk testing ure writer ![]() How independent is that repository, what is the rate of change on that repository, and how big is that repository.īootstrap will be used as the anchor for the whole process. ![]() The main guiding principles are: which group is the primary maintainer of the repository, We will review each repository and discuss what the migration will Nevertheless, you can only check out one of these tag, i.e essentially only In each of the repository are still accessible. That way we willĪvoid name conflict, and the different tags for the same 'history' level Prefixing the name of the repository in front of the tag name. In order to mitigate that, the tag for each imported repository will be renamed, The core issue is that the 'true' history is in fact represented by 20 parallels Time prior to when the actual fusion is done and we have a complete The resulting history, although theoretically complete, is fairly unusable. This technique has the merit of relative simplicity, but the drawback is that The general idea is to consolidate some of these repositories together using a git fetch. Matter for the performance of most git operations, and especially for git clone Libs-core libs-extern libs-extern-sys libs-gui postprocess sdk testingįor reference, the size of the. The migration occurred on August 6th 2011 at 19:30 GMT.īootstrap + artwork base calc components extensions extras filters help impress This page was marked as inactive and is retained for historical reference.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |