[pkg-go] Bug#956117: Syncing git repos is unreliable and cause undefined git repo state

Nicholas D Steeves nsteeves at gmail.com
Tue Jul 21 19:25:11 BST 2020

Hi Simon,

Thank you for replying, and sorry for the delay in my own.

On Tue, Apr 07, 2020 at 06:00:11PM +0200, Simon Frei wrote:
> Syncing a git repository, i.e. .git not the staging area, is prone to
> break: Git has an elaborate structure that needs to stay consistent,
> while Syncthing just sees a huge bunch of files changing very often. If
> e.g. just a part of changed files are synced before a disconnect, that
> immediately renders the git repo in an inconsistent state. For more info
> see e.g.
> https://forum.syncthing.net/t/can-syncthing-reliably-sync-local-git-repos-not-github/8404
> It's probably also mentioned in the linked thread above: Regardless of
> technical limitations, it feels wrong to sync .git. Git is already
> designed to sync changes, i.e. you should use git to sync git. Generally
> stacking sync tools on top of sync tools is quite risky.

Agreed.  Let's keep this bug open until the Debian package contains
documentation warning against this :-)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-go-maintainers/attachments/20200721/1495dc21/attachment.sig>

More information about the Pkg-go-maintainers mailing list