git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Elijah Newren <newren@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Dec 2021, #02; Tue, 7)
Date: Wed, 8 Dec 2021 10:05:47 -0800	[thread overview]
Message-ID: <CABPp-BEd-CLaAJvLpcE=zSinz1up17zh+iUrG--4AXUe765BBA@mail.gmail.com> (raw)
In-Reply-To: <xmqq8rwv6e0a.fsf@gitster.g>

On Wed, Dec 8, 2021 at 1:28 AM Junio C Hamano <gitster@pobox.com> wrote:
>
> Needs an Ack or Reviewed-by.
>  - ns/tmp-objdir                                                12-06          #2

Provided: https://lore.kernel.org/git/CABPp-BEJbS=5i+d-Aa_fCH-WAjSOhX+nSZk5Q9Kb6RiizFg7ZQ@mail.gmail.com/

> Will merge to 'next'?
>  - ld/sparse-diff-blame                                         12-06          #8

I'm in favor.

>  - js/scalar                                                    12-04         #15

Yes, please.  I think everyone agrees there are additional things
wanted, but the current patch series is good (and is already on the
longer side), and it was always designed as the initial submission
with 4-5 additional series coming.  Those additional things can come
in one of the future series.

>  - en/name-rev-shorter-output                                   12-04          #1

Dscho spoke up in favor of merging down
(https://lore.kernel.org/git/nycvar.QRO.7.76.6.2112081237310.90@tvgsbejvaqbjf.bet/),
and you did too 3 weeks ago when you commented,

"""
In any case, this seems to give us a much better results than the
current code, so let's take it and leave further futzing outside the
scope.
"""
(from https://lore.kernel.org/git/xmqq35nv416j.fsf@gitster.g/)

I haven't changed the code since this comment of yours, just added
some additional pointers in the commit message for future readers who
want to tackle that "further futzing".  :-)

  parent reply	other threads:[~2021-12-08 18:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08  2:12 What's cooking in git.git (Dec 2021, #02; Tue, 7) Junio C Hamano
2021-12-08  4:02 ` Eric Sunshine
2021-12-08 18:05 ` Elijah Newren [this message]
2021-12-08 19:57 ` ld/sparse-diff-blame, was " Lessley Dennington
2021-12-08 20:18   ` Elijah Newren
2021-12-08 21:13   ` Junio C Hamano
2021-12-08 22:58     ` Lessley Dennington
2021-12-09  0:22       ` 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='CABPp-BEd-CLaAJvLpcE=zSinz1up17zh+iUrG--4AXUe765BBA@mail.gmail.com' \
    --to=newren@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 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).