All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dickson Wong <dicksonwong@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] mergetool: reorder vim/gvim buffers in three-way diffs
Date: Thu, 11 Feb 2016 12:10:33 -0800	[thread overview]
Message-ID: <CAB8-sypQmomwbq6Fv5OKUbdtBBK5mnuwWg2eAbun9L_K0QcUmA@mail.gmail.com> (raw)
In-Reply-To: <xmqqtwlfvyau.fsf@gitster.mtv.corp.google.com>

On 11 February 2016 at 11:31, Junio C Hamano <gitster@pobox.com> wrote:
> So it should suffice to mention it in the release notes as one
> bullet item that describes one positive change, among all other
> updates described in a simlar way.  And there is no special
> "warnings for existing users" necessary, I would say.

It's unlikely anyone would move the merged window to the top as a
preference only without being aware of the original inconsistency.
If someone has been using a workaround, it would be fairly obvious
as to what has changed, and definitely more so than when they first
encountered the original behavior. Any adjustments to the new behavior
would probably be a workflow change rather than a system configuration
or scripting change.

  reply	other threads:[~2016-02-11 20:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-29  2:18 [PATCH] mergetool: reorder vim/gvim buffers in three-way diffs Dickson Wong
2016-01-29 18:45 ` Junio C Hamano
2016-02-09 22:25   ` Junio C Hamano
2016-02-10 14:40     ` Michael J Gruber
2016-02-10 17:45       ` Junio C Hamano
2016-02-11 15:44         ` Michael J Gruber
2016-02-11 16:03           ` Junio C Hamano
2016-02-11 19:24             ` Dickson Wong
2016-02-11 19:31               ` Junio C Hamano
2016-02-11 20:10                 ` Dickson Wong [this message]
2016-02-11 21:15             ` David Aguilar
2016-02-12 18:15               ` Junio C Hamano

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=CAB8-sypQmomwbq6Fv5OKUbdtBBK5mnuwWg2eAbun9L_K0QcUmA@mail.gmail.com \
    --to=dicksonwong@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 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.