On 20.02.19 10:19, Ævar Arnfjörð Bjarmason wrote:
Most git users are at the level of only knowing very basic add/commit/pull/push command interaction. I feel strongly that we need to make our tools safe to use by default, and not require some relatively advanced "precious"/attribute facility to be carefully configured in advance so we don't throw away uncommitted work on the likes of merge/checkout. 1. https://public-inbox.org/git/87zhuf3gs0.fsf@xxxxxxxxxxxxxxxxxxx/ 2. https://public-inbox.org/git/871s7r4wuv.fsf@xxxxxxxxxxxxxxxxxxx/
+1 Please consider that silently deleting files is a no-go. I teach computer science, and our switch from subversion to git for our second year programming projects caused a lot of grief, so much that my colleagues consider switching back to subversion as the point of first contact with revisioning. Silently deleting partially revisioned files is a major source: students regularly destroy IDE or OS specific config files that they cannot restore themselves. (Project participants use all kinds of different IDEs on different OSs and thus have all kinds of weird hidden files that always manage to get checked into the repository, wreaking havoc on another's machine. So they get deleted and thus disturb the student that needed those files.) We do provide a huge .gitignore that ought to prevent this, but despite numerous warnings they only add it later, which then causes previously checked-in files to be lost upon switching between branches. Please, by default, issue at least a warning before files are irrevocably los - or maybe keep a local snapshot of everything for the last few checkout in order to undo them? Thanks, Steffen. -- +49-89-2180-9139 http://www.tcs.ifi.lmu.de/~jost/ Lehr- und Forschungseinheit für Theoretische Informatik Ludwig-Maximilians-Universität München Oettingenstr. 67 (E111) 80538 München BAVARIA
