diff --git a/README.qmd b/README.qmd index ed9d18d7a279049fa4fa0a981a92a75e690a937c..f96d39ce6b94c2451cd7edb7e89d4c2f5bb1db68 100644 --- a/README.qmd +++ b/README.qmd @@ -716,8 +716,8 @@ When you produce some results for a particular project, you may want to share th When pushing archives to a remote folder, you lose the file deduplication between them. So make sure to push only the archives you want to share with other. ::: -::: {.callout-important} -When pulling archives from a remote folder, you can pull archives produced by others for an unrelated project or even **tar file** not produced by borg. Make sure to specify the good remote path for your project. +::: {.callout-note} +When pulling archives from a remote folder, gblk will ensure that the archive name corresponds to an exiting commit in your git project. ::: ## Remotes @@ -840,15 +840,16 @@ PATH Clone must be used with a *path* and not a remote name. ::: -::: {.callout-important} -When cloning archives from a remote folder, you can pull archives produced by others for an unrelated project or even **tar file** not produced by borg. Make sure to specify the good path for your project. +::: {.callout-note} +When cloning archives from a remote folder, gblk will ensure that all archive names correspond to exiting commits in your git project. ::: + Here are the steps that the clone command execute: 1. Checks if the current folder (or any parent folder) is a git repository 2. Checks if the results folder exits -3. Checks if the remote dir exits and contains tar file +3. Checks if the remote dir exits and contains tar file having commit names 4. Initialize a .borg repository (`gblk init`) 5. Add a local remote called `origin` into the local config file 6. Pull every archive from that remote path diff --git a/slides/slides.qmd b/slides/slides.qmd index 81079f839a2e7f3d223171536b41f49da5779669..d16d367d96b55511468b2e07b8a37447036f1191 100644 --- a/slides/slides.qmd +++ b/slides/slides.qmd @@ -1236,8 +1236,8 @@ When pushing archives to a remote folder, you lose the file deduplication betwee . . . -::: {.callout-important} -When pulling archives from a remote folder, you can pull archives produced by others for an unrelated project or even **tar file** not produced by borg. Make sure to specify the good remote path for your project. +::: {.callout-note} +When pulling archives from a remote folder, gblk will ensure that the archive name corresponds to an exiting commit in your git project. ::: ## gblk configuration file - Remotes @@ -1389,7 +1389,7 @@ Here are the steps that the clone command execute: 2. Checks if the results folder exits :::: :::: {.fragment .fade-in .small-margin} -3. Checks if the remote dir exits and contains tar file +3. Checks if the remote dir exits and contains tar file having commit names :::: :::: {.fragment .fade-in .small-margin} 4. Initialize a .borg repository (`gblk init`)