All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: git@vger.kernel.org, sunshine@sunshineco.com, jrnieder@gmail.com,
	peff@peff.net
Subject: Re: [PATCH v3 2/3] patch-id: document new behaviour
Date: Thu, 03 Apr 2014 08:42:46 -0700	[thread overview]
Message-ID: <xmqqa9c2s9l5.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140402190243.GA13425@redhat.com> (Michael S. Tsirkin's message of "Wed, 2 Apr 2014 22:02:43 +0300")

"Michael S. Tsirkin" <mst@redhat.com> writes:

> So I think I prefer using an option and not a heuristic if you
> are fine with that.

Sure. Changing behaviour only by explicit user request (command line
or configuration) is much safer than heuristics that does not work
reliably.

  reply	other threads:[~2014-04-03 15:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-30 18:09 [PATCH v3 1/3] patch-id: make it stable against hunk reordering Michael S. Tsirkin
2014-03-30 18:09 ` [PATCH v3 2/3] patch-id: document new behaviour Michael S. Tsirkin
2014-03-31 19:08   ` Junio C Hamano
2014-03-31 19:26     ` Michael S. Tsirkin
2014-03-31 19:54       ` Junio C Hamano
2014-03-31 20:42         ` Michael S. Tsirkin
2014-04-02 18:18           ` Junio C Hamano
2014-04-02 19:02             ` Michael S. Tsirkin
2014-04-03 15:42               ` Junio C Hamano [this message]
2014-03-30 18:09 ` [PATCH v3 3/3] patch-id-test: test --stable and --unstable flags Michael S. Tsirkin
2014-03-31 19:29   ` Junio C Hamano
2014-03-31 17:59 ` [PATCH v3 1/3] patch-id: make it stable against hunk reordering Junio C Hamano
2014-03-31 19:04   ` Michael S. Tsirkin
2014-03-31 19:35     ` Junio C Hamano
2014-03-31 22:05 ` 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=xmqqa9c2s9l5.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=mst@redhat.com \
    --cc=peff@peff.net \
    --cc=sunshine@sunshineco.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.