Date: Sun, 27 Aug 2023 07:45:59 +0000 From: bugzilla-noreply@freebsd.org To: doc@FreeBSD.org Subject: [Bug 255323] FreeBSD Handbook: document gitup Message-ID: <bug-255323-9-WPJU83DNqw@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-255323-9@https.bugs.freebsd.org/bugzilla/> References: <bug-255323-9@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255323 Matthias Andree <mandree@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mandree@FreeBSD.org --- Comment #21 from Matthias Andree <mandree@FreeBSD.org> --- I seriously wonder what's with portsnap reliability. In the early days and with my system crashing due to HW issues and broken file systems, I managed= to break things, but nothing that a "rm -rf /usr/ports ; portsnap fetch extrac= t" could not have fixed in a flash. The same about people finding git overcomplex. A port user who is not developing anything will never use format-patch, apply/am, thereabouts, but= I will provoke things a bit and claim that everyone corrupting their git chec= kout have tried to cheat the git tool, followed outdated incorrect third-party documentation, or have an otherwise unreliable system that crashed (checkin= g on fsync() or thereabouts).=20=20 Before we use {SVNTOOL}up - concretely gitup - at scale, we never know what= its quirks are and how reliable things are, but I see it's immature (for instan= ce, https://github.com/johnmehr/gitup/issues/94 as filed by Graham) I have yet (knocking on wood) to see a corrupted Git repo from official Git tools following Git recommendations.=20=20 I personally would not want to distract people and fellow FreeBSD developer= s by recommending a tool that has issues (see Vladimir's exhibits in the comments above) and that I personally do not know and - in a port developer/contribu= tor, committer role - do not want to waste time with. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255323-9-WPJU83DNqw>