Skip to content
Snippets Groups Projects
Commit 55f15c92 authored by ovari's avatar ovari Committed by Adrien Béraud
Browse files

developer/new-developers/submitting-your-first-patch: cleanup

Follow up to patch: https://review.jami.net/c/jami-docs/+/30004

Change 2 consecutive newlines to 1 newline as per SFL convention.

Change-Id: I568b568de6f5e601ae0cebab410626a098067857
parent 416a13ff
No related branches found
No related tags found
No related merge requests found
# Submitting your first patch
## Setting up Git and SSH
(**To work smoothly with Gerrit.**)
First see:
* [Creating a gerrit review](working-with-gerrit)
### SSH setup
<https://review.jami.net/Documentation/user-upload.html#ssh>
......@@ -30,7 +27,6 @@ Your public key has been saved in `jami_gerrit_review.pub`.
3. Set up your local SSH (via `ssh-add` or in `~/.ssh/config`)
4. Test all of the above (SSH on the service or just try to clone a repo on Gerrit via SSH)
### Your Repository
This *assumes* you have moved any existing project clone out of the way.
......@@ -44,13 +40,12 @@ A shell script, to be installed to .git/hooks/commit-msg.
The script creates a unique Change_Id:hash for each commit made from your repository.
- The first time you attempt a _push_ to review `git push origin HEAD:refs/for/master`,
* The first time you attempt a _push_ to review `git push origin HEAD:refs/for/master`,
gerrit will notice a lack of Change-Id.
- Gerrit will also present a secure copy (scp) string.
* Gerrit will also present a secure copy (scp) string.
Use *that* to download a copy of .git/hooks/commit-msg.
## References
+ [Some Gritty Details](https://review.jami.net/Documentation/user-upload.html#_gritty_details)
+ [Some Gritty Details](https://review.jami.net/Documentation/user-upload.html#_gritty_details)
\ No newline at end of file
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment