All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Lessley Dennington <lessleydennington@gmail.com>
Cc: git@vger.kernel.org, "Elijah Newren" <newren@gmail.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Taylor Blau" <me@ttaylorr.com>
Subject: Re: ld/sparse-diff-blame, was What's cooking in git.git (Dec 2021, #02; Tue, 7)
Date: Wed, 08 Dec 2021 16:22:30 -0800	[thread overview]
Message-ID: <xmqqlf0uwrsp.fsf@gitster.g> (raw)
In-Reply-To: <3478ff65-b1ce-5b5c-2053-90b927b66779@gmail.com> (Lessley Dennington's message of "Wed, 8 Dec 2021 16:58:44 -0600")

Lessley Dennington <lessleydennington@gmail.com> writes:

> On 12/8/21 1:13 PM, Junio C Hamano wrote:
>
>> I think the patches in this series are in good shape.  The other
>> topic this series depends on is already in 'next', so we can mark
>> this for 'next', too.
>>
>> Note that "explanation in reply" does not count as much as an
>> improved version would.  If the code or the log message puzzled a
>> reviewer during the review, future readers of the code and "git log"
>> will be puzzled the same way.
>> Thanks.
>> 
> Thank you for the feedback, I will take that into account for future
> series.

This topic in turn is depended on others, so it is in everybody's
interest to declare it stable as soon as we agree it is, and we just
did ;-)

Thanks for working on this.

      reply	other threads:[~2021-12-09  0:22 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
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 [this message]

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=xmqqlf0uwrsp.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=lessleydennington@gmail.com \
    --cc=me@ttaylorr.com \
    --cc=newren@gmail.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.