SVN:externals equivalent in Git?

by

Git has two approaches similar to, but not exactly equivalent to svn:externals:

  • Subtree merges insert the external project’s code into a separate sub-directory within your repo. This has a detailed process to set up and then is very easy for other users, because it is automatically included when the repository is checked out or cloned. This can be a convenient way to include a dependency in your project.
    It is easy to pull changes from the other project, but complicated to submit changes back. And if the other project have to merge from your code, the project histories get merged and the two projects effectively become one.

  • Git submodules (manual) link to a particular commit in another project’s repository, much like svn:externals with an -r argument. Submodules are easy to set up, but all users have to manage the submodules, which are not automatically included in checkouts (or clones).
    Although it is easy to submit changes back to the other project, doing so may cause problems if the repo has changed. Therefore it is generally not appropriate to submit changes back to a project that is under active development.

More Related Contents:

  1. How do I migrate an SVN repository with history to a new Git repository?
  2. Describe your workflow of using version control (VCS or DVCS) [closed]
  3. Cloning a Non-Standard Svn Repository with Git-Svn
  4. Why is Git better than Subversion?
  5. Pushing an existing Git repository to SVN
  6. Why are git submodules incompatible with svn externals?
  7. How and/or why is merging in Git better than in SVN?
  8. How does Git solve the merging problem? [closed]
  9. Why is branching and merging easier in Mercurial than in Subversion?
  10. How to have ‘git log’ show filenames like ‘svn log -v’
  11. Why should I use version control? [closed]
  12. How do you deal with configuration files in source control?
  13. Is git-svn dcommit after merging in git dangerous?
  14. To put the prefix ? to codes by Git/SVN
  15. What are the relative strengths and weaknesses of Git, Mercurial, and Bazaar? [closed]
  16. Can we finally move to DVCS in Corporate Software? Is SVN still a ‘must have’ for development? [closed]
  17. Partial Commits with Subversion
  18. Using Git to work with subversion: Ignoring modifications to tracked files
  19. How to import svn branches and tags into git-svn?
  20. What makes merging in DVCS easy?
  21. Dealing with SVN keyword expansion with git-svn
  22. What makes some version control systems better at merging?
  23. Handling renames: svn vs. git vs. mercurial
  24. svn commit error [closed]
  25. How to git-svn clone the last n revisions from a Subversion repository?
  26. Do I really need version control? [closed]
  27. Getting the last revision number in SVN?
  28. Is there a Subversion Checkout Hook or something similar?
  29. One SVN repository or many?
  30. How can I force subversion to commit an unchanged file?

Leave a Comment