mailing list mirror (one of many)
 help / Atom feed
From: Stefan Beller <>
To: Junio C Hamano <>
Cc: "" <>
Subject: Re: What's cooking in git.git (May 2017, #08; Mon, 29)
Date: Tue, 30 May 2017 10:42:10 -0700
Message-ID: <> (raw)
In-Reply-To: <>

On Sun, May 28, 2017 at 11:23 PM, Junio C Hamano <> wrote:

> A bit more topics are now in 'master'.  One unfortunate thing is
> that the SHA1 breakage in 2.13 for big-endian platforms were lost in
> the noise with excitement felt by some subset of contributors with
> the possible use of submodules.

I am sorry about being excited, without considering the immediate
pressing issues.

> The first step in the series is
> neutral to the excitement, and should be fast-tracked down to
> 'maint' soonish.

Yes I agree on that. Thanks for being calm and unexcited about that!

> * sb/diff-color-move (2017-05-25) 17 commits
>  - diff.c: color moved lines differently
>  "git diff" has been taught to optionally paint new lines that are
>  the same as deleted lines elsewhere differently from genuinely new
>  lines.

My current understanding is that we agree on having the first n-1 patches
in good shape[1] and are only discussing how the exact line coloring
algorithm should look like, so I resent that separately[2]. While
it has better documentation and tests (also a command line option)
Philip still found some issues in there, so I will revisit that patch once


> * sb/submodule-blanket-recursive (2017-05-23) 6 commits
>  Retracted for now.
>  cf. <>

And the retraction is retracted by sending a new series.
You remarked that it still misbehaves with other series in flight,
so I'll inspect it again.

  parent reply index

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-29  6:23 Junio C Hamano
2017-05-29  7:51 ` Samuel Lijin
2017-05-30  0:35   ` Junio C Hamano
2017-05-30 17:42 ` Stefan Beller [this message]
2017-05-30 23:07   ` Junio C Hamano
2017-05-31  3:18 ` Daniel Ferreira (theiostream)
2017-05-31  5:58   ` Stefan Beller
2017-05-31 18:59 ` Ævar Arnfjörð Bjarmason
2017-06-01  0:48   ` Junio C Hamano

Reply instructions:

You may reply publically 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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link mailing list mirror (one of many)

Archives are clonable:
	git clone --mirror
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

Newsgroups are available over NNTP:

 note: .onion URLs require Tor:
       or Tor2web:

AGPL code for this site: git clone public-inbox