Re: What's cooking in git.git (Jun 2023, #08; Fri, 30)

From: Vinayak Dev <vinayakdev.sci@gmail.com>
Date: Jul 1, 2023, 08:14 UTC
Message-ID: <CADE8NarZ7B8VC2cnh4Vt8o0YyNswguXDeJtfEk=9_isHzv4SNg@mail.gmail.com>
In-Reply-To: <xmqq5y747l16.fsf@gitster.g>

On Sat, 1 Jul 2023 at 02:24, Junio C Hamano <gitster@pobox.com> wrote:

Show 10 quoted lines

>
> 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 and may be annotated with an URL
> to a message that raises issues but they are no means exhaustive.  A
> topic without enough support may be discarded after a long period of
> no activity (of course they can be resubmit when new interests
> arise).

Show 9 quoted lines

> * vd/adjust-mfow-doc-to-updated-headers (2023-06-29) 1 commit
>  - docs: include "trace.h" in MyFirstObjectWalk.txt
>
>  Code snippets in a tutorial document no longer compiled after
>  recent header shuffling, which have been corrected.
>
>  Will merge to 'next'?
>  source: <20230629185238.58961-1-vinayakdev.sci@gmail.com>
>

I found an error in this patch while fixing Emily's branch to which the tutorial points, which I linked in a prior mail[1]. This would also require "hex.h" to be added down in the tutorial where the function oid_to_hex() has been called. Accordingly, I have fixed this mistake and rebased, and will send it as a resubmission. That should allow the code to compile properly.

[1]: https://lore.kernel.org/git/CADE8NapQK2ouy4YDQA+3NNkUn_EegkSBQCtDfcSCVGmZvVufXg@mail.gmail.com/

Thanks a lot! Vinayak