git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2022, #02; Fri, 8)
Date: Sun, 10 Jul 2022 15:56:48 -0700	[thread overview]
Message-ID: <xmqqk08kpoen.fsf@gitster.g> (raw)
In-Reply-To: <xmqq4jzquiok.fsf@gitster.g> (Junio C. Hamano's message of "Sat, 09 Jul 2022 13:36:59 -0700")

Junio C Hamano <gitster@pobox.com> writes:

> Here are the topics that have been cooking in my tree.  Commits
> prefixed with '+' are in 'next' (being in 'next' is a sign that a
> topic is stable enough to be used and are candidate to be in a
> future release).  Commits prefixed with '-' are only in 'seen',
> and aren't considered "accepted" at all.

In this edition of the report, the topics that were kept on hold in
the 'next' branch were by mistake left with the "Will cook in 'next'"
label, but please consider them as "Will merge to 'master'" material.

Namely, the following 6 topics are already marked for 'master' in my
updated copy of the "What's cooking" report and will be merged down
accordingly.

> * cr/setup-bug-typo (2022-06-17) 1 commit
> * jk/optim-promisor-object-enumeration (2022-06-16) 1 commit
> * rs/archive-with-internal-gzip (2022-06-15) 6 commits
> * ds/branch-checked-out (2022-06-21) 7 commits
> * jc/resolve-undo (2022-06-09) 1 commit
> * ac/bitmap-format-doc (2022-06-16) 3 commits

Thanks.

      parent reply	other threads:[~2022-07-10 22:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-09 20:36 What's cooking in git.git (Jul 2022, #02; Fri, 8) Junio C Hamano
2022-07-10 12:32 ` lilinchao
2022-07-10 16:28   ` Junio C Hamano
2022-07-10 17:54     ` lilinchao
2022-07-11  0:46       ` Junio C Hamano
2022-07-11  6:17         ` lilinchao
2022-07-10 22:56 ` 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

  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=xmqqk08kpoen.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    /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).