![]() JdkHgCommitMessage : BugIdLine+ SummaryLine? ReviewersLine ContributedByLine? ![]() A commit message for the Mercurial jdk/jdk repository has It uses the git-fast-import protocol to import MercurialĬhangesets into Git, and it adjusts existing commit messages to align with Gitīest practices. We have already prototyped a program to convert a Mercurial repository to a Git Lastly, there are many options available for hosting Git repositories, whether There are multiple desktop clients available for interacting with Git Git integration out-of-the-box, including There are many more tools for interacting with Git than Mercurial:Īll text editors have Git integration, either natively or in the form ofĪlmost all integrated development environments (IDEs) also ship with Users who do not need the entire history. That only clone parts of the history, resulting in even less metadata for those Since fewer bits have to go over the wire. ![]() The reduction in metadata preserves local disk space and reduces clone times, Is around 1.2 GB with Mercurial, depending on the Mercurial version being used. The jdk/jdk repository is approximately 300 MB with Git and the. The size of the version control metadata. Initial prototypes of converted repositories show a significant reduction in Size of version control system metadata.There are three primary reasons for migrating to Git: We will not propose changes to the current JDK development process, though That issue is the topic of JEP 369: Migrate to GitHub. This JEP does not address the question of whether OpenJDK Git repositories willīe self-hosted or hosted by an external provider. Longer term, a Mercurial URL to Git URL translator might be put into place. The existing master Mercurial repos will at least be kept as read-only archives for a defined transition period. We will not aggressively decommission the existing Mercurial repos or take other actions to prematurely invalidate the many URLs pointing into the repos, such as in comments in bugs in JBS. We will not change the bug system from JBS. Those Projects can migrate to Git ifĪnd when they consolidate into a single repository. We will not migrate multi-repository OpenJDK Projects, such as the Create a tool to translate between Mercurial and Git hashes.Reformat commit messages according to Git best practices.Preserve all version control history, including tags.Migrate all single-repository OpenJDK Projects from Mercurial to Git.Migrate the OpenJDK Community's source code repositories from Mercurial (hg)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |