Re: GSoC 2016: applications open, deadline = Fri, 19/2

From: Lars Schneider <larsxschneider@gmail.com>
Date: Feb 17, 2016, 18:32 UTC
Message-ID: <448280D1-3EEB-40DF-9886-C9B620E32E3C@gmail.com>
In-Reply-To: <20160217172407.GD1831@hank>

On 17 Feb 2016, at 18:24, Thomas Gummerer <t.gummerer@gmail.com> wrote:

Show 22 quoted lines

> 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@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html