You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: book/07-git-tools/sections/submodules.asc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ Suppose you’re developing a website and creating Atom feeds.
10
10
Instead of writing your own Atom-generating code, you decide to use a library.
11
11
You’re likely to have to either include this code from a shared library like a CPAN install or Ruby gem, or copy the source code into your own project tree.
12
12
The issue with including the library is that it’s difficult to customize the library in any way and often more difficult to deploy it, because you need to make sure every client has that library available.
13
-
The issue with vendoring the code into your own project is that any custom changes you make are difficult to merge when upstream changes become available.
13
+
The issue with copying the code into your own project is that any custom changes you make are difficult to merge when upstream changes become available.
14
14
15
15
Git addresses this issue using submodules.
16
16
Submodules allow you to keep a Git repository as a subdirectory of another Git repository.
0 commit comments