public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH 2/2] doc/user_manual: Add reference to GPG tutorial
Date: Wed, 24 Jul 2019 22:33:03 +0200	[thread overview]
Message-ID: <20190724203303.11549-2-mosipov@ilbers.de> (raw)
In-Reply-To: <20190724203303.11549-1-mosipov@ilbers.de>

Signed-off-by: Maxim Yu. Osipov <mosipov@isar-build.org>
---
 doc/user_manual.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/doc/user_manual.md b/doc/user_manual.md
index ed181aa..d8ada2c 100644
--- a/doc/user_manual.md
+++ b/doc/user_manual.md
@@ -780,7 +780,7 @@ Cache upstream debian packages to reduce time for further downloads and to be ab
  - Signing of local repo (optional)
 
 By default, the local caching repo is not gpg signed. If you want to share it in a trusted way, you may sign it.
-To do that, install `gpg` in your build environment, import the public and private keys,
+To do that, install `gpg` in your build environment, import the public and private keys (see [1] for details),
 and provide the path to the public key in `conf/local.conf`, e.g.:
 
 ```
@@ -851,3 +851,5 @@ And build the corresponding image target:
 ```
 bitbake multiconfig:qemuarm64-stretch:isar-image-base
 ```
+
+[1] GPG Turorial What is GPG?  https://theprivacyguide.org/tutorials/gpg.html
-- 
2.11.0


  reply	other threads:[~2019-07-24 20:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-24 20:33 [PATCH 1/2] ci_build: Add signing cached repo test Maxim Yu. Osipov
2019-07-24 20:33 ` Maxim Yu. Osipov [this message]
2019-07-25  6:52 ` Henning Schild
2019-07-25 16:38   ` Baurzhan Ismagulov
2019-07-25 19:30   ` Baurzhan Ismagulov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190724203303.11549-2-mosipov@ilbers.de \
    --to=mosipov@ilbers.de \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox