From: "Philip Oakley" Sent: March 14, 2016 9:08 PM
From: "Lars Schneider"
On 14 Mar 2016, at 07:57, Junio C Hamano wrote:
Lars Schneider writes:
I thought a while about this requirement and I wonder if a wrapper
called
'ggit' (guarded Git) could be a solution. The wrapper would pass all
Junio C Hamano writes:
> Lars Schneider writes:
>
>> On 14 Mar 2016, at 07:57, Junio C Hamano wrote:
>>
>>> I recall back in the days when people said that Hg's command set was
>>> so much more pleasant to use that some people thought about building
>>> Hg's command line UI on top of low level
Sidhant Sharma writes:
> On Monday 14 March 2016 01:46 PM, Lars Schneider wrote:
>
>> I also thought about (2). The obvious advantage of having something like
>> "ggit" as part of Git core is that it would be shipped with the standard
>> Git distribution. That would especially help beginners.
Y
On Sunday 20 March 2016 09:38 PM, Lars Schneider wrote:
> On 20 Mar 2016, at 16:51, Sidhant Sharma 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 comf
On 20 Mar 2016, at 16:51, Sidhant Sharma 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,
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
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 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 wil
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, 'ggi
From: "Lars Schneider"
On 14 Mar 2016, at 07:57, Junio C Hamano wrote:
Lars Schneider writes:
I thought a while about this requirement and I wonder if a wrapper
called
'ggit' (guarded Git) could be a solution. The wrapper would pass all
command line arguments to 'git' and check for poten
Lars Schneider writes:
> On 14 Mar 2016, at 07:57, Junio C Hamano wrote:
>
>> I recall back in the days when people said that Hg's command set was
>> so much more pleasant to use that some people thought about building
>> Hg's command line UI on top of low level implementation of the Git's
>> da
On Monday 14 March 2016 11:44 AM, Jacob Keller wrote:
> On Sun, Mar 13, 2016 at 10:25 PM, Sidhant Sharma
> wrote:
>> On Monday 14 March 2016 04:58 AM, Jacob Keller wrote:
>>>
>>> If I recall correctly, a configuration setting was previously
>>> discussed but mostly discarded as a solution since
On Monday 14 March 2016 01:46 PM, Lars Schneider wrote:
> On 14 Mar 2016, at 07:57, Junio C Hamano wrote:
>
>> If "ggit" is made too limited, there is an issue. Beginners may at
>> some point need to transition to the real thing to fully exploit the
>> power of Git, and they may need to unlearn "
On 14 Mar 2016, at 07:57, Junio C Hamano wrote:
> Lars Schneider writes:
>
>> I thought a while about this requirement and I wonder if a wrapper called
>> 'ggit' (guarded Git) could be a solution. The wrapper would pass all
>> command line arguments to 'git' and check for potentially destruc
Kevin Daudt writes:
> On Mon, Mar 14, 2016 at 12:03:33AM +0530, Sidhant Sharma wrote:
>>
>>
>>
>> Other than this, I also tried to expand the list of potentially destructive
>> commands and updated the list as follows (additions in brackets):
>>
>> * git rebase [ git pull --rebase ]
>> * git
Lars Schneider writes:
> I thought a while about this requirement and I wonder if a wrapper called
> 'ggit' (guarded Git) could be a solution. The wrapper would pass all
> command line arguments to 'git' and check for potentially destructive
> commands. If such a command is detected then the u
On Sun, Mar 13, 2016 at 10:25 PM, Sidhant Sharma wrote:
>
> On Monday 14 March 2016 02:49 AM, Kevin Daudt wrote:
>> On Mon, Mar 14, 2016 at 12:03:33AM +0530, Sidhant Sharma wrote:
>>> Other than this, I also tried to expand the list of potentially destructive
>>> commands and updated the list as f
On Sun, Mar 13, 2016 at 10:25 PM, Sidhant Sharma wrote:
>
> On Monday 14 March 2016 04:58 AM, Jacob Keller wrote:
>> On Sun, Mar 13, 2016 at 11:33 AM, Sidhant Sharma
>> wrote:
>>> Coincidentally, my approach too is a wrapper around git as you suggest.
>>> The approach is simple and straight forw
On Monday 14 March 2016 02:49 AM, Kevin Daudt wrote:
> On Mon, Mar 14, 2016 at 12:03:33AM +0530, Sidhant Sharma wrote:
>> Other than this, I also tried to expand the list of potentially destructive
>> commands and updated the list as follows (additions in brackets):
>>
>> * git rebase [ git pull -
On Monday 14 March 2016 04:58 AM, Jacob Keller wrote:
> On Sun, Mar 13, 2016 at 11:33 AM, Sidhant Sharma
> wrote:
>> Coincidentally, my approach too is a wrapper around git as you suggest.
>> The approach is simple and straight forward, but I wasn't sure if it would be
>> accepted on the list, m
On Sun, Mar 13, 2016 at 11:33 AM, Sidhant Sharma wrote:
> Coincidentally, my approach too is a wrapper around git as you suggest.
> The approach is simple and straight forward, but I wasn't sure if it would be
> accepted on the list, mainly because it may not look consistent with the
> current
>
On Mon, Mar 14, 2016 at 12:03:33AM +0530, Sidhant Sharma wrote:
>
>
>
> Other than this, I also tried to expand the list of potentially destructive
> commands and updated the list as follows (additions in brackets):
>
> * git rebase [ git pull --rebase ]
> * git reset --hard
> * git clean -f
>
On Sunday 13 March 2016 09:20 PM, Lars Schneider wrote:
> Hi Sidhant,
>
> thanks for your interest in the 'Git Beginner' mode topic. I completely
> understand your motivation for the topic as your Git learning experience
> matches mine. However, please be aware that this is no easy project. The
Hi Sidhant,
thanks for your interest in the 'Git Beginner' mode topic. I completely
understand your motivation for the topic as your Git learning experience
matches mine. However, please be aware that this is no easy project. The
final implementation might be easy but it will require hard work to
Hi everyone!
I am Sidhant Sharma, from Delhi, India. I'm a third year Software Engineering
student at Delhi Technological University. I am looking to contribute to
Git via GSoC 2016. I have also worked on one of the microprojects [1]. I've
been using git for nearly two years now, and continue to b
24 matches
Mail list logo
