Overview
| Comment: | README.md: Add a paragraph about unsigned checkins |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
0ea86b888989e4399122b20a45a7e216 |
| User & Date: | js on 2021-10-31 20:42:23 |
| Other Links: | manifest | tags |
Context
|
2021-10-31
| ||
| 20:45 | Merge support for notifications check-in: 78fbf22685 user: js tags: trunk | |
| 20:42 | README.md: Add a paragraph about unsigned checkins check-in: 0ea86b8889 user: js tags: trunk | |
| 16:00 | Make GCC happy again check-in: 4efb0135d5 user: js tags: trunk | |
Changes
Modified README.md from [df7d0bd20b] to [6acd9cb987].
| ︙ | ︙ | |||
119 120 121 122 123 124 125 126 127 128 129 130 131 132 |
you have multiple working directories all backed by the same local
repository.
In order to verify the signature of the currently checked out checkin, you
can use:
$ fossil artifact current | gpg --verify
<h2 id="cloning-git">Git</h2>
To clone the Git repository, use the following:
$ git clone https://github.com/ObjFW/ObjFW
| > > > > > > | 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 |
you have multiple working directories all backed by the same local
repository.
In order to verify the signature of the currently checked out checkin, you
can use:
$ fossil artifact current | gpg --verify
Please note that not all checkins are signed, as the signing key only resides
on trusted systems. This means that checkins I perform on e.g. Windows are
unsigned. However, usually it should not take long until there is another
signed checkin. Alternatively, you can go back until the last signed checkin
and review changes from there on.
<h2 id="cloning-git">Git</h2>
To clone the Git repository, use the following:
$ git clone https://github.com/ObjFW/ObjFW
|
| ︙ | ︙ |