git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Nelson Benitez Leon <nelsonjesus.benitez@seap.minhap.es>,
	git@vger.kernel.org
Subject: Re: [PATCH] rebase -i: inform the user they can re-order commits
Date: Fri, 16 Mar 2012 07:46:19 -0700	[thread overview]
Message-ID: <7vhaxoioxw.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <vpq3998ehp3.fsf@bauges.imag.fr> (Matthieu Moy's message of "Fri, 16 Mar 2012 15:36:24 +0100")

Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:

> Junio C Hamano <gitster@pobox.com> writes:
>
>> Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
>>
>>> 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.
>>
>> I was not questioning that "You can also reorder" is dangerous in any way.
>>
>> What is dangerous is to give an illusion that it is safe to use "rebase
>> -i" without reading a decent documentation that does not even say that
>> reordering is one of the primary purpose of the command, and the mindset
>> that it is OK to give such an illusion with these reminder lines.
>
> Yes, but my point is that you can already do that. Nelson just gave an
> example when explaining how he came out with this patch.

Yes, I know that.

And a patch like this will _encourage_ the users to follow that path even
more. Is it a good thing?  That is what I was questioning.

  reply	other threads:[~2012-03-16 14:46 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
2012-03-16 14:26         ` Junio C Hamano
2012-03-16 14:36           ` Matthieu Moy
2012-03-16 14:46             ` Junio C Hamano [this message]
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=7vhaxoioxw.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --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 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).