Skip to content

Commit a1ac0a9

Browse files
committed
Replace the obscure term 'vendoring' with 'copying'
1 parent a10851b commit a1ac0a9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

book/07-git-tools/sections/submodules.asc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ Suppose you’re developing a web site and creating Atom feeds.
1010
Instead of writing your own Atom-generating code, you decide to use a library.
1111
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.
1212
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.
1414

1515
Git addresses this issue using submodules.
1616
Submodules allow you to keep a Git repository as a subdirectory of another Git repository.

0 commit comments

Comments
 (0)