Use Git aliases in local contribution guide
1 unresolved thread
1 unresolved thread
Merge request reports
Activity
added Content Refinement label
Resolved by Martin Schroschkvielen Dank für den MR.
Welche Vorteile siehst du bei der Verwendung von Git aliases gegenüber normalen Shell aliases? Wenn man öfter mit dem Repo arbeitet, speichert man die Shell aliases sicherlich auch in einer File und sourct diese dann vor der Verwendung (oder man speichert die aliases gleich in der
~/.bashrco.Ä.). D.h. die Anzahl der Handschläge ist vergleichbar.- Last reply by Martin Schroschk
requested review from @mflehmig--tu-dresden.de
assigned to @mflehmig--tu-dresden.de
83 83 needs to be downloaded, but you have to run it only once in a while. 84 84 Building a container could be done with the following steps: 85 85 86 ```bash 87 cd hpc-wiki 88 doc.zih.tu-dresden.de/util/download-newest-mermaid.js.sh 89 docker build -t hpc-compendium . 86 ```console 87 marie@local$ cd hpc-wiki changed this line in version 2 of the diff
-
I think this is wrong now. In the "Initial Setup of your Local Clone " it states:
- Change to a local (unencrypted) filesystem. (We have seen problems running the container on an
ecryptfs filesystem. So you might want to use e.g.
/tmpas the start directory.) - Create a new directory, e.g. with
mkdir hpc-wiki - Change into the new directory, e.g.
cd hpc-wiki
So it should clearly be
cd hpc-wiki. - Change to a local (unencrypted) filesystem. (We have seen problems running the container on an
ecryptfs filesystem. So you might want to use e.g.
mentioned in commit 404d638c
Please register or sign in to reply