From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
From: Nextcloud bot <bot@nextcloud.com>
Date: Nov, 01 2026 09:29:59 +0000
Subject: [PATCH] <short summary of the patch>

TODO: Put a short summary on the line above and replace this paragraph
with a longer explanation of this change. Complete the meta-information
with other relevant fields (see below for details). To make it easier, the
information below has been extracted from the changelog. Adjust it or drop
it.

---
The information above should follow the Patch Tagging Guidelines, please
checkout https://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: (upstream|backport|vendor|other), (<patch-url>|commit:<commit-id>)
Bug: <upstream-bugtracker-url>
Bug-<Vendor>: <vendor-bugtracker-url>
Forwarded: (no|not-needed|<patch-forwarded-url>)
Applied-Upstream: <version>, (<commit-url>|commit:<commid-id>)
Reviewed-By: <name and email of someone who approved/reviewed the patch>

--- nextcloud-desktop-35.0.50-20261101.092853.9937c91e4c.orig/git2changelog.cfg
+++ nextcloud-desktop-35.0.50-20261101.092853.9937c91e4c/git2changelog.cfg
@@ -1,7 +1,7 @@
 # Use the configuration below with appropriate changes,
 # if you want to support a new client version using
 # your own fork. In such a case the tags do not come
-# across to the main repo for a pull request, so
+# accross to the main repo for a pull request, so
 # some hacking is needed
 [versionhack]
 commit = bc7e65b39552ac458b2adacf76cbf98735ec29a0
