All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Linus Arver <linusa@google.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2023, #05; Fri, 15)
Date: Wed, 20 Sep 2023 07:57:18 -0700	[thread overview]
Message-ID: <xmqqjzskdh9t.fsf@gitster.g> (raw)
In-Reply-To: <owly1qetjqo1.fsf@fine.c.googlers.com> (Linus Arver's message of "Tue, 19 Sep 2023 23:37:50 -0700")

Linus Arver <linusa@google.com> writes:

>> Whatever improvements you have in mind, if they are
>> minor, letting the above graduate (they have been in 'next' for a
>> week without anybody complaining) and doing them as a follow-up
>> series would be sensible, I would think.
>>
>> Thanks.
>
> Hmm, I don't think they are minor? See
> https://github.com/listx/git/tree/trailer-libification-prep for the
> current state of things.

They do not look like "oops the patches I sent to the list was
totally bogus and they need replacing"; aren't they rather "these
are not yet complete and there are some of the follow-on work on top
of them"?

> I need to still follow up to your last comment on "trailer: rename
> *_DEFAULT enums to *_UNSPECIFIED" [2] (I was going to see if we needed
> the "obvious solution" as you described).
>
> If it's too painful to move this out of 'next' now, I'm OK with it
> graduating as is and doing a separate follow-up (I expect several more
> of these to happen anyway). Up to you.

Let's mark the topic as "waiting for follow-up updates" and keep it
in 'next' until the follow-up patches become ready, then.

> Sorry for not noticing that this was in 'next' sooner and communicating
> accordingly.

Gotchas happen.  Let's try to communicate better the next time.

Thanks.

  reply	other threads:[~2023-09-20 14:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-16  1:41 What's cooking in git.git (Sep 2023, #05; Fri, 15) Junio C Hamano
2023-09-19 18:32 ` Taylor Blau
2023-09-24 19:59   ` SZEDER Gábor
2023-09-25 23:06     ` Taylor Blau
2023-09-19 20:00 ` Linus Arver
2023-09-19 20:16   ` Junio C Hamano
2023-09-19 21:25   ` Junio C Hamano
2023-09-20  6:37     ` Linus Arver
2023-09-20 14:57       ` Junio C Hamano [this message]
2023-09-20 19:20         ` Linus Arver

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=xmqqjzskdh9t.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=linusa@google.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.