Skip to content
Snippets Groups Projects
Select Git revision
  • 8a72b48bf7112f5dcd515cb46ac7534daa492566
  • master default
  • anders.blomdell
  • typeref
  • pragma
  • compiler-refactoring
  • labcomm2013
  • v2014.1
  • v2014.0
  • v2013.0
10 results

labcomm_decoder.c

Blame
  • Forked from Anders Blomdell / LabComm
    Source project has a limited visibility.
    slides.tex 2.58 KiB
    \documentclass[handout]{beamer}
    
    \usetheme{Control}
    
    
    % \usepackage{palatino}
    % \usepackage{tikz}
    \usepackage{listings}
    \usepackage{pgfpages}
    \pgfpagesuselayout{4 on 1}[a4paper, border shrink=5mm, landscape]
    
    \title{Git Tutorial\\ \tiny{Version: 0.5}}
    \author{Anders Nilsson  \texttt{andersn@control.lth.se}}
    \date[LU 160304]{Lund 2016-03-04}
    
    \lstset{
      frame=single,
      basicstyle=\footnotesize\ttfamily
    }
    
    
    \begin{document}
    \frame{\titlepage}
    
    
    
    
    \section{Introduction}
    \label{sec:intro}
    
    \frame{
      \frametitle{Why?}
      \onslide <1>\pgfimage[height=.9\textheight]{figures/phd101212s.png}
    }
    \frame{
      \frametitle{Why?}
      \onslide <1>\pgfimage[height=.9\textheight]{chaos.png}
    }
    \frame{
      \frametitle{What?}
      \onslide <1->\pgfimage[height=.8\textheight]{figures/git.png}
    }
    \frame{
      \frametitle{For the matematicians}
      \onslide <1->\pgfimage[height=.5\textheight]{figures/hilbert.jpg}
    }
    
    \frame{
      \frametitle{How?}
      \pgfimage[width=.9\textwidth]{lifecycle.png}
    }
    
    
    \frame{
      \frametitle{Version Control?}
      \begin{itemize} [<+-| alert@+>]
      \item Why version control?
      \item What is version control?
      \item How to do?
      \end{itemize}
    }
    
    
    \frame{
      \frametitle{Why?}
    }
    
    \frame{
      \frametitle{Why?}
      \begin{description}[<+-| alert@+>]
      \item[Backups:] With version control you always have previous versions
        of your files available, if you happen to do something stupid like
        erasing a file. Or just regret a large edit later on.
      \item[Organization:] Knowing which copy of a project directory is up
        to date, and which ones are not, saves a lot of time and problems.
      \item[Collaboration:] Everyone who has tried to collaborate with other
        people by sending files, or parts of files, over email knows how
        fragile that is.
      \end{description}
    
    }
    
    
    \frame{
      \frametitle{What is it?}
      \begin{itemize}
      \item Numerous tools: CVS, Subversion, Git, Team Foundation, Clearcase, ...
      \item Different architectures; centralized repository, or distributed. 
      \end{itemize}
    }
    
    \frame{
      \frametitle{What is Git?}
      \begin{itemize}
      \item Git is free, both as in speech and in beer, unlike Clearcase,
        Team Foundation and other commercial systems.
      \item Git is distributed. When each user has her own repository copy
        you do not always need to have contact with a central server. 
      \item There is a large Internet community around git making it easy to
        find information and/or help when needed.
      \item It is used in some large high profile open source projects. Most
        known is the Linux kernel.
      \end{itemize}
    }
    
    
    \frame{
      \frametitle{How?}
      \pgfimage[width=.9\textwidth]{lifecycle.png}
    }
    
    
    
    \end{document}