summaryrefslogtreecommitdiff
path: root/_posts/2009-10-10-subtree-merge.textile
diff options
context:
space:
mode:
authortekkub <tekkub@gmail.com>2010-07-12 19:05:59 -0600
committertekkub <tekkub@gmail.com>2010-07-12 19:05:59 -0600
commitc2ee51c311467177997cfd595f23ec656f1286f7 (patch)
tree02d781853b8692f376c1be4ce4b70738fb77faf7 /_posts/2009-10-10-subtree-merge.textile
parentf985030efd5c7c4b8445265613a6274c182aff3e (diff)
Handle spacey category names differently
Diffstat (limited to '_posts/2009-10-10-subtree-merge.textile')
-rw-r--r--_posts/2009-10-10-subtree-merge.textile2
1 files changed, 1 insertions, 1 deletions
diff --git a/_posts/2009-10-10-subtree-merge.textile b/_posts/2009-10-10-subtree-merge.textile
index b9d7474..c2b3fd3 100644
--- a/_posts/2009-10-10-subtree-merge.textile
+++ b/_posts/2009-10-10-subtree-merge.textile
@@ -2,7 +2,7 @@
layout: default
title: Working with subtree merge
description: How to use subtree merge to merge one repo into another as a subpath.
-categories: "Git ninjutsu"
+categories: git_ninjutsu
---
There are times when submodules are not adequate for the task at hand. For example, blending multiple repos together into one single repo while still maintaining the histor of each repo. To do this, the subtree merge strategy is a better solution.