From: Lars Schneider <larsxschneider@gmail.com>
To: Sidhant Sharma <tigerkid001@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>,
Jacob Keller <jacob.keller@gmail.com>, Kevin Daudt <me@ikke.info>,
philipoakley@iee.org
Subject: Re: [RFC/GSoC] Introduction
Date: Sun, 20 Mar 2016 16:39:32 +0100 [thread overview]
Message-ID: <33EDD26C-ED5A-42EE-B523-240AEF5C51B7@gmail.com> (raw)
In-Reply-To: <56EAC49B.6020909@gmail.com>
Hi Sidhant,
that sounds about right to me. In what language do you plan to implement the
wrapper?
Best,
Lars
On 17 Mar 2016, at 15:52, Sidhant Sharma <tigerkid001@gmail.com> wrote:
> Hi,
>
> So to sum up, the list of tasks for the project would be:
> 1. A wrapper is to be implemented around (called 'ggit') that will scan the
> arguments for potentially destructive commands. When none are found, all the
> arguments will simply be passed through to git.
> 2. If such a command is found, 'ggit' will:
> a. Show what the command is actually going to do.
> b. Ask the user if they are sure they want to execute it.
> Eg. "You are about to do X which will permanently destroy Y. Do you want to
> continue?"
> 3. For all commands that are entered, 'ggit' will also show a brief summary of
> the command what it will do when executed, explaining it's intended usage.
>
> Is the list correct, or did I miss something?
>
>
> Thanks and regards,
> Sidhant Sharma
next prev parent reply other threads:[~2016-03-20 15:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-12 6:59 [RFC/GSoC] Introduction Sidhant Sharma
2016-03-13 15:50 ` Lars Schneider
2016-03-13 18:33 ` Sidhant Sharma
2016-03-13 21:19 ` Kevin Daudt
2016-03-14 5:25 ` Sidhant Sharma
2016-03-14 6:15 ` Jacob Keller
2016-03-14 7:01 ` Junio C Hamano
2016-03-13 23:28 ` Jacob Keller
2016-03-14 5:25 ` Sidhant Sharma
2016-03-14 6:14 ` Jacob Keller
2016-03-14 16:00 ` Sidhant Sharma
2016-03-14 6:57 ` Junio C Hamano
2016-03-14 8:16 ` Lars Schneider
2016-03-14 15:56 ` Sidhant Sharma
2016-03-20 20:17 ` Matthieu Moy
2016-03-14 17:25 ` Junio C Hamano
2016-03-20 20:28 ` Matthieu Moy
2016-03-14 21:08 ` Philip Oakley
2016-03-17 14:52 ` Sidhant Sharma
2016-03-20 15:39 ` Lars Schneider [this message]
2016-03-20 15:51 ` Sidhant Sharma
2016-03-20 16:08 ` Lars Schneider
2016-03-20 16:22 ` Sidhant Sharma
-- strict thread matches above, loose matches on Subject: below --
2016-03-22 17:51 Philip Oakley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=33EDD26C-ED5A-42EE-B523-240AEF5C51B7@gmail.com \
--to=larsxschneider@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jacob.keller@gmail.com \
--cc=me@ikke.info \
--cc=philipoakley@iee.org \
--cc=tigerkid001@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).