Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Git course
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
courses
Git course
Commits
8abb534b
Commit
8abb534b
authored
11 years ago
by
Laros
Browse files
Options
Downloads
Patches
Plain Diff
Updated the skeleton slides.
parent
2af49b64
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
skeleton/skeleton.tex
+38
-7
38 additions, 7 deletions
skeleton/skeleton.tex
with
38 additions
and
7 deletions
skeleton/skeleton.tex
+
38
−
7
View file @
8abb534b
...
...
@@ -45,6 +45,7 @@
\item
Code.
\item
Documentation.
\end{itemize}
\pause
\item
Have the same structure for all projects.
\end{itemize}
\end{frame}
...
...
@@ -215,6 +216,7 @@
\begin{frame}
[fragile]
\frametitle
{
Git annex.
}
Manage files with git, without checking their contents in.
\begin{itemize}
\item
Manage large files without storing them.
\item
Store file checksums.
...
...
@@ -224,6 +226,7 @@
\pause
You first have to enable this for your repository.
\bigskip
\begin{lstlisting}
[language=none, caption=Enable git-annex.]
$
git annex init "<name>"
...
...
@@ -233,13 +236,19 @@
\begin
{
frame
}
[
fragile
]
\frametitle
{
Adding big files.
}
In our master repository, we annex a file.
\bigskip
\begin
{
lstlisting
}
[
language
=
none, caption
=
Adding files.
]
$
git annex add <filename>
$
git commit
\end
{
lstlisting
}
\bigskip
\pause
In a clone, this file will visible, but not really present.
\bigskip
\begin
{
lstlisting
}
[
language
=
none, caption
=
Make a file available.
]
$
file <filename>
<filename>: broken symbolic link to ...
...
...
@@ -251,14 +260,19 @@
\frametitle
{
Removing files.
}
As long as there are enough copies available, you can remove files.
\bigskip
\begin
{
lstlisting
}
[
language
=
none, caption
=
A failing drop command.
]
$
git annex drop <filename>
drop bigfile (unsafe)
git-annex: drop: 1 failed
\end{lstlisting}
\bigskip
\pause
It is actually quite well protected.
\bigskip
\begin{lstlisting}
[language=none, caption=rm fails too.]
$
rm
-
rf <repository>
rm: cannot remove <repository>
/
.git
/
annex
/
objects
/
...
...
...
@@ -266,21 +280,38 @@
\end
{
frame
}
\begin
{
frame
}
[
fragile
]
\frametitle
{
Sync your results.
}
\frametitle
{
Sync
hronise
your results.
}
Let the other repositories know what you have done.
\begin
{
lstlisting
}
[
language
=
none, caption
=
.
]
\bigskip
\begin
{
lstlisting
}
[
language
=
none, caption
=
Synchronise with all repositories.
]
$
git annex sync
\end{lstlisting}
\bigskip
\pause
You can choose to sync with a selection of repositories.
\bigskip
\begin{lstlisting}
[language=none, caption=Synchronise with a selection.]
$
git annex sync origin
\end
{
lstlisting
}
\end
{
frame
}
\begin
{
frame
}
[
fragile
]
\frametitle
{
Working together on the same clone.
}
If you need to work with other people on the same repository clone on the
Shark cluster, you can use the following command to give group access:
\begin{lstlisting}
[language=none, caption=.]
Sometimes you need to work with other people on the same repository clone.
\begin
{
itemize
}
\item
Where the large files are stored.
\end
{
itemize
}
\bigskip
Use the following command to give group access:
\bigskip
\begin
{
lstlisting
}
[
language
=
none, caption
=
Make everyting group writable.
]
$
find -type d -exec chmod 775
{}
\;
$
find
-
type f
-
exec chmod
664
{}
\;
\end
{
lstlisting
}
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment