In Git you can add a submodule to a repository. This is basically a repository embedded in your main repository. This can be very useful. A couple of usecases of submodules:
- Separate big codebases into multiple repositories.
From 473846959772d8160b34b92ae3bcecddf24b972f Mon Sep 17 00:00:00 2001 | |
From: =?UTF-8?q?Julian=20Nu=C3=9F?= <[email protected]> | |
Date: Tue, 23 Sep 2014 21:07:29 +0200 | |
Subject: [PATCH 1/1] [BUGIFX] Zend Framework 1 + PHP5.6 | |
--- | |
lib/Zend/Locale/Format.php | 22 +++++++++++----------- | |
lib/Zend/Service/Audioscrobbler.php | 6 +++--- | |
lib/Zend/Service/Technorati.php | 6 +++--- | |
lib/Zend/Validate/Hostname.php | 4 ++-- |
#!/bin/sh | |
# $Id: xvfb-run 2027 2004-11-16 14:54:16Z branden $ | |
# This script starts an instance of Xvfb, the "fake" X server, runs a command | |
# with that server available, and kills the X server when done. The return | |
# value of the command becomes the return value of this script, except in cases | |
# where this script encounters an error. | |
# | |
# If anyone is using this to build a Debian package, make sure the package |
At the top of the file there should be a short introduction and/ or overview that explains what the project is. This description should match descriptions added for package managers (Gemspec, package.json, etc.)
Show what the library does as concisely as possible, developers should be able to figure out how your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.