[Bug 255323] FreeBSD Handbook: document gitup

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255323

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 extract"
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 checkout
have tried to cheat the git tool, followed outdated incorrect third-party
documentation, or have an otherwise unreliable system that crashed (checking on
fsync() or thereabouts).  

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 instance,
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.  

I personally would not want to distract people and fellow FreeBSD developers 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/contributor,
committer role - do not want to waste time with.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.