Signed-off-by: Pierre Habouzit <madcoder@debian.org>
%}}}
\section{Why choosing \git}%{{{
%}}}
\section{Why choosing \git}%{{{
-\begin{frame}{It's a DSCM [1/2]}
+\begin{frame}{Because SVN isn't good enough}
I've packaged with SVN on svn.debian.org for a long time…
\uncover<2->{\alert{well, it sucks}:}
\begin{itemize}
I've packaged with SVN on svn.debian.org for a long time…
\uncover<2->{\alert{well, it sucks}:}
\begin{itemize}
\end{itemize}
\end{frame}
\end{itemize}
\end{frame}
-\begin{frame}{It's a DSCM [2/2]}
+\begin{frame}{Because \git{} does what I need}
With \git, as a DSCM, most of the issues are gone.
\begin{itemize}
\item<2-> Off-line work is possible, in fact you always work off-line;
With \git, as a DSCM, most of the issues are gone.
\begin{itemize}
\item<2-> Off-line work is possible, in fact you always work off-line;
\item<5-> \git{} storage is extremely efficient: the marginal cost of
commits decreases with the number of commits.
\end{itemize}
\item<5-> \git{} storage is extremely efficient: the marginal cost of
commits decreases with the number of commits.
\end{itemize}
+\begin{frame}{A bit more about \git{} storage}
+ \git{} storage is very efficient and optimized. Some numbers:
- \uncover<6->{
- GNU libc version 2.7 weights weights 115Mo unpacked. The full glibc
- history (from before 1984) weights less than \alert{120Mo}.
+ \vspace{1em}
+ \uncover<2->{
+ xorg-xserver.git, goes back to 2000, is \alert{20Mo} big. The last
+ orig.tar.gz is 8Mo big, more than 84Mo unpacked.
+ \vspace{1em}
+ \uncover<3->{
+ dpkg.git, whole history since April 1996, generates a git pack of
+ \alert{15Mo}. The last dpkg release is 17Mo big unpacked.
+ }
- \uncover<7->{
- My experience shows that \git{} storage, for a project with quite some
- history, is smaller than 2.5 times the size of the last upstream release
- (unpacked).
+ \vspace{1em}
+ \uncover<4->{
+ GNU libc version 2.7 weights 115Mo unpacked. The full glibc history
+ (starts in the eighties) generates a \git{} pack of \alert{104Mo}.
+ }
+
+ \vspace{1em}
+ \uncover<5->{
+ Though, this won't probably true for packages with a lot of binary stuff
+ in it, where delta compression is less likely to produce good results
+ (games data packages come to mind).
}
\end{frame}
\begin{frame}{A real maintainer toolbox}
}
\end{frame}
\begin{frame}{A real maintainer toolbox}
- Though \git{} is special, because it was designed by a {\bf Maintainer}.
- This has several implications:
+ \git{} is special, because it was designed by a {\bf Maintainer}. This has
+ several implications:
\begin{itemize}
\item<2-> \git{} operations to look at the history are blazingly fast;
\item<3-> \git{} operations to integrate patches are blazingly fast;
\begin{itemize}
\item<2-> \git{} operations to look at the history are blazingly fast;
\item<3-> \git{} operations to integrate patches are blazingly fast;
\vspace{1em}
\uncover<4->{
\vspace{1em}
\uncover<4->{
- And when you're happy of the current sate, let's fake that you're a good
+ And when you're happy of the current sate, let's pretend that you're a good