git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Elijah Newren <newren@gmail.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, Derrick Stolee <derrickstolee@github.com>
Subject: Re: What's cooking in git.git (Nov 2022, #03; Mon, 14)
Date: Tue, 15 Nov 2022 22:07:37 -0800	[thread overview]
Message-ID: <CABPp-BFJDYpOyAz1XGjqu3p9NVwQjFLta6HCux2y26TvLw5kjQ@mail.gmail.com> (raw)
In-Reply-To: <Y3Mag8qG2D3qjlmg@nand.local>

On Mon, Nov 14, 2022 at 9:26 PM Taylor Blau <me@ttaylorr.com> wrote:
> * en/sparse-checkout-design (2022-11-07) 1 commit
>   (merged to 'next' on 2022-11-08 at 42e164b490)
>  + sparse-checkout.txt: new document with sparse-checkout directions
>
>  Design doc.
>
>  Needs review.
>  source: <pull.1367.v4.git.1667714666810.gitgitgadget@gmail.com>

Labelled as "Needs review", but you merged it to next...is the label stale?

If not, Stolee reviewed and said he thinks it's ready to merge
down[*].  I suspect we'll still have some discussions (and I just
responded to some comments from both him and ZheNing), but none appear
to be things that necessitate changes to the document.  And I suspect
discussions are naturally going to continue until we have everything
implemented, and the design doc is a pretty decent starting point as
it is.

[*] https://lore.kernel.org/git/f3345a9e-e7f1-4230-d30a-0608eb69513d@github.com/

  parent reply	other threads:[~2022-11-16  6:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15  4:50 What's cooking in git.git (Nov 2022, #03; Mon, 14) Taylor Blau
2022-11-15  4:59 ` Eric Sunshine
2022-11-15  5:01   ` Taylor Blau
2022-11-15  6:28 ` ps/receive-use-only-advertised Patrick Steinhardt
2022-11-15  6:47   ` ps/receive-use-only-advertised Taylor Blau
2022-11-15 17:28     ` ps/receive-use-only-advertised Jeff King
2022-11-16  2:02       ` ps/receive-use-only-advertised Taylor Blau
2022-11-18 23:27       ` ps/receive-use-only-advertised Junio C Hamano
2022-11-15  8:06 ` rp/maintenance-qol with 'make DEVELOPER=1' (was: What's cooking in git.git (Nov 2022, #03; Mon, 14)) Ævar Arnfjörð Bjarmason
2022-11-15 14:04 ` ms/sendemail-validate-headers, was Re: What's cooking in git.git (Nov 2022, #03; Mon, 14) Johannes Schindelin
2022-11-16  1:20   ` Taylor Blau
2022-11-16 11:48     ` Strawbridge, Michael
2022-11-18 13:24       ` Johannes Schindelin
2022-11-15 20:58 ` Eric Sunshine
2022-11-16  2:04   ` Taylor Blau
2022-11-16  6:07 ` Elijah Newren [this message]
2022-11-16 20:16   ` Taylor Blau

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=CABPp-BFJDYpOyAz1XGjqu3p9NVwQjFLta6HCux2y26TvLw5kjQ@mail.gmail.com \
    --to=newren@gmail.com \
    --cc=derrickstolee@github.com \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).