git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2024, #02; Fri, 1)
Date: Mon, 4 Nov 2024 20:51:43 -0500	[thread overview]
Message-ID: <7be6cc82-e566-4425-b663-71e53117af3d@gmail.com> (raw)
In-Reply-To: <xmqqikt2wrn1.fsf@gitster.g>

On 11/4/24 5:39 PM, Junio C Hamano wrote:
> Taylor Blau <me@ttaylorr.com> writes:
> 
>>> [Graduated to 'master']
>>>
>>> * ds/path-walk-1 (2024-10-31) 6 commits
  - path-walk: mark trees and blobs as UNINTERESTING
  - path-walk: visit tags and cached objects
  - path-walk: allow consumer to specify object types
  - t6601: add helper for testing path-walk API
  - test-lib-functions: add test_cmp_sorted
  - path-walk: introduce an object walk by path

>> This is marked as "Graduated to 'master'", although I suspect it isn't.
>> I thought that it would have been because the topic went away, although
>> I still see this in 'jch' via your 3503a15e17 (Merge branch
>> 'kh/bundle-docs' into jch, 2024-11-03).
>>
>> Perhaps this WC report was generated before moving the topic back into
>> 'jch'? In either event, as noted by <ZyUqr/wb5K4Og9j9@nand.local>, this
>> topic is still under discussion and is not ready to be merged (yet).
> 
> I am not sure how exactly it happened, but IIRC, the topic branch for
> this one was missing for some time after I grabbed the broken-out
> topics from you.  As I didn't rebuild 'seen' I managed to pull it
> out of master..seen chain locally, but that was before I generated
> the "What's cooking" report and I think that is how this entry was
> mistakenly moved.
It is possible that things got confusing when this replaced
ds/path-walk, which was a longer series that started with these same
patches.

Thanks,
-Stolee


  reply	other threads:[~2024-11-05  1:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04  4:05 What's cooking in git.git (Nov 2024, #02; Fri, 1) Junio C Hamano
2024-11-04 15:29 ` Taylor Blau
2024-11-04 22:39   ` Junio C Hamano
2024-11-05  1:51     ` Derrick Stolee [this message]
2024-11-05 20:54 ` Bence Ferdinandy
2024-11-06  0:19   ` Junio C Hamano
2024-11-09  8:51     ` Bence Ferdinandy

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=7be6cc82-e566-4425-b663-71e53117af3d@gmail.com \
    --to=stolee@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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.
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).