summaryrefslogtreecommitdiff
path: root/src/git-in-reverse.tex
diff options
context:
space:
mode:
authorkballou <kballou@devnulllabs.io>2016-03-16 12:00:43 -0600
committerkballou <kballou@devnulllabs.io>2016-03-16 12:18:43 -0600
commit61ddbb131acbc85ae3746c4bbdb913db0d9ea289 (patch)
treec3740aab191057179c3e11c59d320010cd529a1d /src/git-in-reverse.tex
parentf9a709f5e9705d1e59fcdfdd35d05359e2d22f13 (diff)
downloadgit-in-reverse-61ddbb131acbc85ae3746c4bbdb913db0d9ea289.tar.gz
git-in-reverse-61ddbb131acbc85ae3746c4bbdb913db0d9ea289.tar.xz
Merge subtree in tikz image
Instead of using `dashed` style and duplicating the node, the ideal display was the same node, which this change achieves by adding an extra draw call after the trees are defined.
Diffstat (limited to 'src/git-in-reverse.tex')
-rw-r--r--src/git-in-reverse.tex11
1 files changed, 5 insertions, 6 deletions
diff --git a/src/git-in-reverse.tex b/src/git-in-reverse.tex
index f7f23e4..c9d6c0f 100644
--- a/src/git-in-reverse.tex
+++ b/src/git-in-reverse.tex
@@ -364,17 +364,16 @@ What does Git store?
\begin{figure}
\begin{tikzpicture}[sibling distance=3cm]
\node at (0, 0) {Current Tree}
- child{node[text=solarizedMagenta] {68b75754}
+ child{node[text=solarizedMagenta] (new_tree) {68b75754}
child{node[text=solarizedBlue] {a3f555b64}
- child{node[text=solarizedGreen]{foo 2}}}
- child{node[text=solarizedBlue,dashed] {5716ca598}
- child{node[text=solarizedGreen,dashed] {bar}}}};
- \node at (5, 0) {Old Tree}
+ child{node[text=solarizedGreen]{foo 2}}}};
+ \node at (4, 0) {Old Tree}
child{node[text=solarizedMagenta] {b98c9a9f}
- child{node[text=solarizedBlue] {5716ca598}
+ child{node[text=solarizedBlue] (bar_hash) {5716ca598}
child{node[text=solarizedGreen] {bar}}}
child{node[text=solarizedBlue] {257cc5642}
child{node[text=solarizedGreen]{foo}}}};
+ \draw[-o,thick] (new_tree) edge (bar_hash);
\end{tikzpicture}
\end{figure}
\end{frame}