I thought that the grand-parent comment referred to sentences such as this from the article:
"Git can be used as a database for your application."
If you intend to distribute your application, even though you're not copying the git source code directly, nor linking your application directly against a git library, the GPL is rather ambiguous.
"Pipes, sockets and command-line arguments are communication mechanisms normally used between two separate programs. So when they are used for communication, the modules normally are separate programs. But if the semantics of the communication are intimate enough, exchanging complex internal data structures, that too could be a basis to consider the two parts as combined into a larger program." -- http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#Me...
Minor correction: the LGPL relaxes the reciprocity requirement for code that uses the LGPL code; linking isn't the only example, imports in dynamic languages is another.
Re:Uses of git
by icebraining on Thursday February 09, 2012 @12:23PM
(#3571973)
The GPL doesn't have a reciprocity requirement; it's a pay-it-forward system.
Re:Uses of git
by sundar22in on Thursday February 09, 2012 @11:21AM
(#3571686)
Good explanation!
If you incorporate GPLed software into your own software - that is, copy the source code - then your work is considered a derived work and is also under the GPL.
Software that is LGPLed can be linked to without making your application under the GPL itself. This includes things like glibc. (The "L" in "LGPL" used to stand for "Library" but now it means "Lesser.")
Finally, if you use GPL software to produce your own works, there is no effect. So using git to manage your own source has no impact. Same with using gcc to compile your source.