git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: Lars Schneider <larsxschneider@gmail.com>,
	Sidhant Sharma <tigerkid001@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [RFC/GSoC] Introduction
Date: Sun, 20 Mar 2016 21:28:58 +0100	[thread overview]
Message-ID: <vpqlh5c99md.fsf@anie.imag.fr> (raw)
In-Reply-To: <xmqq7fh5as54.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Mon, 14 Mar 2016 10:25:27 -0700")

Junio C Hamano <gitster@pobox.com> writes:

> Lars Schneider <larsxschneider@gmail.com> writes:
>
>> On 14 Mar 2016, at 07:57, Junio C Hamano <gitster@pobox.com> 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
>>> data structure....
>>> ...
>>
>> I think a "ggit" wrapper should not introduce any new commands or
>> new parameters. Everything should be passed unmodified to Git.
>> The wrapper would only add additional warnings...
>
> Somehow I was assuming that you are aiming for a more ambitious
> project, where the users get an easier-to-learn-and-understand
> command line UI experience than bare Git [*1*],

I think the proposed approach makes much more sense, at least because:

* At some point, ggit users should become git users and the transition
  should be smooth.

* ggit users will find advices/documentation/tutorials here and there on
  the web, or talk to their friends who use git, and they want this
  information to apply to ggit.

Also, having an alternative UI sometimes serves as an excuse not to
improve git's UI itself. If git's behavior is dangerous, ggit can warn
about it. If git's behavior is broken, then we should repair it.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

  reply	other threads:[~2016-03-20 20:29 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 [this message]
2016-03-14 21:08       ` Philip Oakley
2016-03-17 14:52   ` Sidhant Sharma
2016-03-20 15:39     ` Lars Schneider
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=vpqlh5c99md.fsf@anie.imag.fr \
    --to=matthieu.moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=larsxschneider@gmail.com \
    --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).