From: Junio C Hamano <gitster@pobox•com>
To: Lars Schneider <larsxschneider@gmail•com>
Cc: Sidhant Sharma <tigerkid001@gmail•com>,
Git Mailing List <git@vger•kernel.org>
Subject: Re: [RFC/GSoC] Introduction
Date: Mon, 14 Mar 2016 10:25:27 -0700 [thread overview]
Message-ID: <xmqq7fh5as54.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <FB2E0900-A77E-4AE2-A580-9192746A8ABA@gmail.com> (Lars Schneider's message of "Mon, 14 Mar 2016 09:16:01 +0100")
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*], but none of what I
said about "limiting and omitting" applies if "ggit" will be a
"passthru after examining what goes on" wrapper.
> Maybe "ggit" could also be interpreted as "guided Git" (sounds more
> friendly than "guarded Git"). I have the impression that many Git
> beginners make mistakes because they don't have a mental model of Git,
> yet. A "guided" Git version could explain the commands a bit more
> detailed as they use Git (e.g. with ASCII graph examples). I know
> that's what man pages are for but I've encountered many users
> (especially on Windows) that are not aware of man pages.
ounds like a lot of work but still a sensible goal. And that leaves
no room for questioning if it is suitable for Git GSOC, at least to
me--it does fall into the scope of making experience of learning
better for Git itself.
Thanks.
[Footnote]
*1* For example, subversion migrants may say it is confusing to call
the command "checkout" that is used to clobber files in the
working tree to the state in the index and may want to call it
"revert"--and "$SCM revert $path" would be the way the more
ambitious project would let its users do that operation; it
would call underlying "git checkout $path" for its users.
There are other command line UI restructuring that will not
belong to Git itself but an alternative UI front-end may want to
use, e.g. "$SCM diff INDEX WORKTREE $pathname" that is turned
into "git diff $pathname" and "$SCM diff HEAD INDEX $pathname"
that is turned into "git diff --cached HEAD $pathname".
next prev parent reply other threads:[~2016-03-14 17: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 [this message]
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
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=xmqq7fh5as54.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=larsxschneider@gmail$(echo .)com \
--cc=tigerkid001@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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