From: Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>
To: Jacob Keller <jacob.keller@gmail•com>
Cc: Junio C Hamano <gitster@pobox•com>,
Sidhant Sharma <tigerkid001@gmail•com>,
Lars Schneider <larsxschneider@gmail•com>,
Git Mailing List <git@vger•kernel.org>,
Philip Oakley <philipoakley@iee•org>
Subject: Re: [RFC/GSOC] Git Beginner | Warnings for potentially destructive commands
Date: Sat, 26 Mar 2016 16:12:37 +0100 [thread overview]
Message-ID: <vpqfuvdi87u.fsf@anie.imag.fr> (raw)
In-Reply-To: <CA+P7+xqkqfccQtWeKbURZt21i+gw=b7f0YHHuqeNzM7TH2m+6g@mail.gmail.com> (Jacob Keller's message of "Fri, 25 Mar 2016 12:20:48 -0700")
Jacob Keller <jacob.keller@gmail•com> writes:
> If possible, I would suggest aiming for generating the actual topology
> that the user is seeing, customized so that it gives relevenat
> information, rather than static examples.
Using the real topology in a useful way is actually pretty hard. It's
quite easy to throw the output of "git log --graph --oneline ..." to the
user, but as soon as the rebase deals with more than a handfull of
commits, we'd want to simplify the history to show something
understandable to the user (which by definition should be a beginner if
he uses ggit), like replacing long sequences of commits with "..." or
so. That is hard to get right.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2016-03-26 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 10:18 [RFC/GSOC] Git Beginner | Warnings for potentially destructive commands Sidhant Sharma
2016-03-25 17:38 ` Junio C Hamano
2016-03-25 19:20 ` Jacob Keller
2016-03-26 15:12 ` Matthieu Moy [this message]
2016-03-27 7:36 ` Jacob Keller
2016-03-29 6:13 ` Sidhant Sharma
2016-03-30 15:57 ` [RFC/GSOC] Git Beginner | Warnings for potentially destructive commands (v2) Sidhant Sharma
2016-03-31 7:59 ` Remi Galan Alfonso
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=vpqfuvdi87u.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp$(echo .)fr \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=jacob.keller@gmail$(echo .)com \
--cc=larsxschneider@gmail$(echo .)com \
--cc=philipoakley@iee$(echo .)org \
--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