all repos — website @ e239a3a726d94593051f52270386e6f9dba81bb6

My website

Convert front matter for zola

Alan Pearce
commit

e239a3a726d94593051f52270386e6f9dba81bb6

parent

f7464d1d29af7a4777637617ff3e7a7845e234a7

1 file changed, 4 insertions(+), 4 deletions(-)

changed files
M post/git-cloning-similar-repositories.mdpost/git-cloning-similar-repositories.md
@@ -1,9 +1,9 @@
+++ -Categories = ["Development"] -Description = "Speed up cloning of similar git repositories" -Tags = ["git"] +description = "Speed up cloning of similar git repositories" title = "Cloning Similar Git Repositories" date = 2014-06-22T08:35:24Z +[taxonomies] +tags = ["git"] +++ With multiple similar git repositories, for example where a base repository contains a framework or base system installation and other repositories are created from that repository, it's possible to save some time when cloning down another repository by using the `reference` option to [git-clone][]:
@@ -16,4 +16,4 @@ On a related note, I'm surprised that [GitHub][] doesn't allow for multiple renamed forks, which would be very useful in this scenario. [BitBucket][] does support this, however. It even has a 'sync' button for pulling updates from the base into the child repositories, which is very useful, especially for those who prefer GUIs over CLIs.
[git-clone]:https://www.kernel.org/pub/software/scm/git/docs/git-clone.html [GitHub]:https://github.com -[BitBucket]:https://bitbucket.org/+[BitBucket]:https://bitbucket.org/