Mercurial > lilug > scm
changeset 10:424847edab23
How does it work, issues for centralized systems
author | Josef "Jeff" Sipek <jeffpc@optonline.net> |
---|---|
date | Mon, 12 Sep 2005 19:04:02 -0400 |
parents | 3f79b90f35ba |
children | 35a431953a9d |
files | Makefile client-server-layout.dot slideshow.tex |
diffstat | 3 files changed, 29 insertions(+), 5 deletions(-) [+] |
line wrap: on
line diff
--- a/Makefile Mon Sep 12 19:02:47 2005 -0400 +++ b/Makefile Mon Sep 12 19:04:02 2005 -0400 @@ -11,6 +11,7 @@ dot -Tps client-server-checkout.dot -o client-server-checkout.ps dot -Tps client-server-modified.dot -o client-server-modified.ps dot -Tps client-server-commit.dot -o client-server-commit.ps + dot -Tps client-server-layout.dot -o client-server-layout.ps clean: rm -f *~ *.pdf *.ps *.dvi *.log *.out *.aux
--- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/client-server-layout.dot Mon Sep 12 19:04:02 2005 -0400 @@ -0,0 +1,9 @@ +digraph G { + size ="4,4"; + repository [shape=record,label="Repository | {data store | interface}"]; + network [shape=ellipse]; + user [shape=record,label="Client | {interface | user}"]; + + repository -> network; + network -> user; +}
--- a/slideshow.tex Mon Sep 12 19:02:47 2005 -0400 +++ b/slideshow.tex Mon Sep 12 19:04:02 2005 -0400 @@ -26,16 +26,26 @@ \overlays{3}{ \begin{slide}{What can it do?} \begin{itemstep} - \item Keep revision history + \item Keep revision history % I may say files with code, but I really mean any file - it doesn't have to be code \item Revert to any revision \item Track down who changed particular line of code \end{itemstep} \end{slide}} +% How does it work? - typical workflow +\overlays{1}{ +\begin{slide}{How does it work?} + \begin{itemstep} + \item Repository % You have a repository, it stores all the data and metadata + \item Check out the source % the repository contains the history and should not be touched directly + \item Edit % edit to your heart's content + \item Commit % commit - or save - the changes to the repository; creating the revision history (timestamp, comment) + \end{itemstep} +\end{slide}} + \overlays{4}{ \begin{slide}{Client-Server (eg. Subversion)} \begin{center} - % FIXME: animation of what happens \onlySlide*{1}{\includegraphics{client-server.ps}} % - server, client \onlySlide*{2}{\includegraphics{client-server-checkout.ps}} % - client checks out a copy \onlySlide*{3}{\includegraphics{client-server-modified.ps}} % - client modifies code @@ -43,9 +53,13 @@ \end{center} \end{slide}} -% issues: -% non-commiters are second class citizens -% promotes the use of patches - bad! why have SCM when you use patches?! +\overlays{2}{ +\begin{slide}{Client-Server - Issues} + \begin{itemstep} + \item Non-commiters are \emph{second class citizens} + \item Promotes use of patches - bad! why have SCM when you use patches?! + \end{itemstep} +\end{slide}} \overlays{2}{ \begin{slide}{Distributed (eg. Mercurial)}