From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Nelson Benitez Leon <nelsonjesus.benitez@seap.minhap.es>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] rebase -i: inform the user they can re-order commits
Date: Fri, 16 Mar 2012 15:12:39 +0100 [thread overview]
Message-ID: <vpqaa3geiso.fsf@bauges.imag.fr> (raw)
In-Reply-To: <4F63571D.4070405@seap.minhap.es> (Nelson Benitez Leon's message of "Fri, 16 Mar 2012 16:07:09 +0100")
Nelson Benitez Leon <nelsonjesus.benitez@seap.minhap.es> writes:
> On 03/16/2012 01:17 PM, Junio C Hamano wrote:
>> If the user does not even know that one of the primary use of the command
>> is to reorder, isn't he playing with fire?
>
> In an ideal world everybody should study the manpages and documentation of
> a program prior to using it, unfortunately most people often start with an
> easy-to-follow tutorial where there are commands to type in, the user
> will type them (confident in the tutorial reputation) and try to learn along
> the way, in this case giving the user more indications about what he can
> do in any moment is, in my opinion, a good thing (as git already does).
The case of "rebase" is a bit different, since "rebase" is potentially
dangerous.
But if the user sees the help message of "rebase -i", then I don't think
we will stop him from breaking anything by not mentionning that
reordering commits can work. We already give other commands that rewrite
history with more or less danger, so the additional messages isn't
really harmful.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2012-03-16 14:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 11:13 [PATCH] rebase -i: inform the user they can re-order commits Nelson Benitez Leon
2012-03-16 10:21 ` Matthieu Moy
2012-03-16 11:34 ` Nelson Benitez Leon
2012-03-16 11:53 ` Matthieu Moy
2012-03-16 13:36 ` Jakub Narebski
2012-03-16 12:17 ` Junio C Hamano
2012-03-16 15:07 ` Nelson Benitez Leon
2012-03-16 14:12 ` Matthieu Moy [this message]
2012-03-16 14:26 ` Junio C Hamano
2012-03-16 14:36 ` Matthieu Moy
2012-03-16 14:46 ` Junio C Hamano
2012-03-16 14:39 ` Junio C Hamano
2012-03-20 23:07 ` Junio C Hamano
2012-03-21 8:25 ` Matthieu Moy
2012-03-21 10:45 ` 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=vpqaa3geiso.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nelsonjesus.benitez@seap.minhap.es \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.