Commit 58d4f7bd authored by Judit Foglszinger's avatar Judit Foglszinger

Adding editorial changes by tumbleweed

- Capitalizing titles.
- Capitalizing abbreviation for CC-BY-SA
- Starting bullet points with capital letter and end with full stop where appropriate.
- Wrapping git-lfs and .gitattributes into backticks.
parent 4096a682
......@@ -6,12 +6,12 @@ and appropriate to share with the world.
We do not have infinite amounts of disk space, so please use common sense before uploading huge files.
## web
## Web
All files in the repository can be accessed via the web:
<https://salsa.debian.org/debconf-team/public/share/debconf19>
## setup
## Setup
All Debian developers (DDs) can directly push to this repository.
Others can either open a merge request or ask any DD for commit rights.
......@@ -20,19 +20,19 @@ The repository is using git lfs (git large file system).
This makes handling of big files more efficient, but requires some additional attention
when adding files to the repository.
1. you need the package git-lfs
1. on Debian systems from buster on `# apt install git-lfs`
1. for stretch install from backports, see documentation on https://backports.debian.org/
1. You need the package `git-lfs`.
1. On Debian systems from buster on `# apt install git-lfs`
1. For stretch install from backports, see documentation on https://backports.debian.org/.
You probably do not want to `git clone` the repo, as git-lfs will download *everything*
inside it. To do a shallow clone:
1. `$ GIT_LFS_SKIP_SMUDGE=1 git clone --config filter.lfs.smudge=true git@salsa.debian.org:debconf-team/public/share/debconf19.git`
1. `$ cd debconf19`
1. lfs files are now only stored as references. To actually fetch a file, run `git lfs fetch -I <filename>`
1. lfs files are now only stored as references. To actually fetch a file, run `git lfs fetch -I <filename>`.
1. Use it mostly as though it were a normal git repository. To add files, see below.
## adding files
## Adding files
Adding files generally works like it normally would in git.
Ensure that the files you add actually end up in lfs by
......@@ -49,9 +49,9 @@ If the file is not there, check whether the file pattern is tracked by lfs:
If it's not there either, if it makes sense, rename the file to match one pattern
or see git-lfs documentation (eg <https://docs.gitlab.com/ee/workflow/lfs/manage_large_binaries_with_git_lfs.html>)
on how to add your extension.
When doing so, don't forget to either commit/push .gitattributes or to include it in your merge request.
When doing so, don't forget to either commit/push `.gitattributes` or to include it in your merge request.
## license
## License
License for all files uploaded: cc-by-sa 4.0 unless explicitly stated otherwise.
License for all files uploaded: CC-BY-SA 4.0 unless explicitly stated otherwise.
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