Commit df7670aa authored by Grégory Mounié's avatar Grégory Mounié
Browse files

typos

parent 38029253
......@@ -113,7 +113,7 @@ single file and a first commit.
$ mkdir MiniRepo
$ cd MiniRepo
$ git init .
$ emacs file.txt # add few lines
$ emacs file.txt # add few lines with your editor
$ git add file.txt
$ git commit -m "message 1"
\end{minted}
......@@ -291,7 +291,7 @@ point to the same file.
\section{Headless Git}
This section discuss about ``detached head'': why do you pass in this
This section discusses about ``detached head'': why do you pass in this
state, and what to do to avoid trouble.
\subsection{Get the work directory state of a previous commit}
......@@ -346,7 +346,7 @@ $ git rev-list --all | xargs git grep <PATTERN>
\end{itemize}
In a Git repository, the only easily visible files are in the ancestor
commits of a entry point:
commits of an entry point:
\begin{itemize}
\item branches;
\item tags;
......@@ -384,7 +384,7 @@ $ git commit -m "message dev2"
$ git checkout master
\end{minted}
Comme back to \texttt{develop} and check that the commit is there:
Come back to \texttt{develop} and check that the commit is there:
\begin{minted}{console}
git checkout develop
git log --graph --oneline
......@@ -399,11 +399,11 @@ commit.
If you come back to the tag \texttt{v0.1} from section~\ref{sec:tags},
are you in a detached head state, or not ? Why ?
Try and check !
Try to come back to the tag, and check !
\section{Conclusion\dots{}}
Git data storage is addressable by content. The link between files are
Git data storage is addressable by content. The link between files compose
a direct acyclic graph, with several sources (entry points). Most Git
commands create new nodes, new sources or navigate in the
graph. Understanding this graph management is the main challenge of
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment