On 17 Feb 2016, at 18:24, Thomas Gummerer <t.gummerer@xxxxxxxxx> wrote: > On 02/10, Matthieu Moy wrote: >> Work on the application itself, and on the list of ideas. > > One potential idea: > > Make destructive git commands more safe for the user. > > Some commands (e.g. git reset --hard, git clean -f, etc.) can > potentially destroy some of the users work. Store the information > that we are potentially losing somewhere, where it's easily > retrievable by the user. > > This should probably be hidden behind a new config variable > (core.iKnowWhatImDoingButIReallyDont or something better), as it has > the potential to really inflate the repository size (when storing > binary files that should be deleted by git clean for example). > > It happened more than once that I thought I knew what I was doing, but > would have been really glad if git saved me from my mistakes. > > I haven't thought this through much further than just the idea, so it > would be great to hear some opinions on it first. Coincidentally I started working on similar thing already (1) and I have lots of ideas around it. I get endless requests at my $DAYJOB of messed up Git repos where people just pasted stuff from StackOverflow without a deep understanding of what they are doing. If the lists agrees to take this topic for GSoC I would be happy to co-mentor it. Cheers, Lars (1) using Git config hacks > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html