ObjFW  Check-in [0dc8f1b5cd]

Overview
Comment:README.md: Remove paragraph about opening the repo

The instructions were changed to no longer explicitly open the repo
using `fossil open`, so the paragraph about opening the repo multiple
times no longer makes sense.

Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 0dc8f1b5cdcbff2e7852da4a706533d0732b0a0a703711828d90d0258c92224f
User & Date: js on 2023-10-02 22:38:17
Other Links: manifest | tags
Context
2023-10-08
08:03
ofhttp: Fix missing comma that caused a crash check-in: b21bacd5fd user: js tags: trunk
07:41
Merge trunk into 1.0 branch check-in: 05ccd59b38 user: js tags: 1.0
2023-10-02
22:38
README.md: Remove paragraph about opening the repo check-in: 0dc8f1b5cd user: js tags: trunk
2023-10-01
20:23
OFSystemInfo: Check uname() return against -1 check-in: 12e54c754f user: js tags: trunk
Changes

Modified README.md from [68d2728883] to [ab455f4c69].

137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154

  You can then use Fossil's web interface to browse the timeline, tickets,
  wiki pages, etc.:

    $ cd objfw
    $ fossil ui

  It's also possible to open the same local repository multiple times, so that
  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







<
<
<
<







137
138
139
140
141
142
143




144
145
146
147
148
149
150

  You can then use Fossil's web interface to browse the timeline, tickets,
  wiki pages, etc.:

    $ cd objfw
    $ fossil ui





  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