git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC/GSoC] Introduction

From
Sidhant Sharma <tigerkid001@gmail.com>
Date
Mar 20, 2016, 16:22 UTC
Message-ID
<56EECE2E.4080004@gmail.com>
In-Reply-To
<A0465058-2171-4C00-8D45-C610046C496D@gmail.com>
On Sunday 20 March 2016 09:38 PM, Lars Schneider wrote:
Show 21 quoted lines
> On 20 Mar 2016, at 16:51, Sidhant Sharma <tigerkid001@gmail.com> wrote:
>
>> On Sunday 20 March 2016 09:09 PM, Lars Schneider wrote:
>>> Hi Sidhant,
>>>
>>> that sounds about right to me. In what language do you plan to implement the 
>>> wrapper?
>> I'm comfortable in programming with C, so I think I can use that. Otherwise,
>> I'm also comfortable with python and familiar with bash, if they are required.
>> Would C be the right choice though?
>> Also, I've made a draft proposal for the project and uploaded to the GSoC
>> application site. Should I send it to the list as well for RFC?
> Although I like Python a lot, I don't think it would be a good choice. AFAIK Git
> core does not depend on Python and therefore you can't really expect a Python
> interpreter in every Git environment (e.g. it is not part of Git for Windows).
>
> The wrapper could certainly be implemented in C, although I don't know if this 
> would make things harder then they need to be. My initial thought was to use a
> scripting language that is known to be shipped with Git (Bash or Perl). I
> think Perl might even have an advantage as it offers very good regex/string
> processing functions (disclaimer: I am no Perl expert at all...).
Okay, I'll get started with Perl right away, shouldn't take long.
Show 32 quoted lines
> Please post your draft proposal as plain text RFC to the list.
>
> Thanks,
> Lars
>
>
>> Thanks,
>> Sidhant Sharma
>>> 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
Previous: Lars Schneider
Message 23 of 23 in “[RFC/GSoC] Introduction”
  1. Sidhant SharmaMar 12, 2016
  2. Lars SchneiderMar 13, 2016
  3. Sidhant SharmaMar 13, 2016
  4. Kevin DaudtMar 13, 2016
  5. Sidhant SharmaMar 14, 2016
  6. Jacob KellerMar 14, 2016
  7. Junio C HamanoMar 14, 2016
  8. Jacob KellerMar 13, 2016
  9. Sidhant SharmaMar 14, 2016
  10. Jacob KellerMar 14, 2016
  11. Sidhant SharmaMar 14, 2016
  12. Junio C HamanoMar 14, 2016
  13. Lars SchneiderMar 14, 2016
  14. Sidhant SharmaMar 14, 2016
  15. Matthieu MoyMar 20, 2016
  16. Junio C HamanoMar 14, 2016
  17. Matthieu MoyMar 20, 2016
  18. Philip OakleyMar 14, 2016
  19. Sidhant SharmaMar 17, 2016
  20. Lars SchneiderMar 20, 2016
  21. Sidhant SharmaMar 20, 2016
  22. Lars SchneiderMar 20, 2016
  23. Sidhant SharmaMar 20, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.