From: shejialuo <shejialuo@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2025, #01; Fri, 3)
Date: Sat, 4 Jan 2025 12:12:26 +0800 [thread overview]
Message-ID: <Z3i1Kgf9M_AiBMBr@ArchLinux> (raw)
In-Reply-To: <xmqqjzbbpp6f.fsf@gitster.g>
On Fri, Jan 03, 2025 at 01:23:20PM -0800, Junio C Hamano wrote:
> [New Topics]
>
> * ja/doc-commit-markup-updates (2025-01-03) 3 commits
> - doc: git-commit: migrate secondary files to new format
> - doc: git-commit.txt: convert git commit config to new format
> - doc: git-commit: apply new documentation guidelines
>
> Doc updates.
>
> source: <pull.1845.git.1735912046.gitgitgadget@gmail.com>
>
>
> * jc/doc-opt-tilde-expand (2025-01-03) 1 commit
> (merged to 'next' on 2025-01-03 at b3e6e7acbc)
> + gitcli.txt: typeset pathnames as monospace
>
> Docfix.
>
> Will merge to 'next' and then to 'master'.
> source: <6e0abe96b60a94d4fdee15a45b7d53c2f44a0c69.1735903029.git.martin.agren@gmail.com>
>
>
> * mh/doc-windows-home-env (2025-01-03) 1 commit
> (merged to 'next' on 2025-01-03 at 1d4db69ce0)
> + git.txt: fix heading line of tildes
>
> Docfix.
>
> Will merge to 'next' and then to 'master'.
> source: <50e47d14a8a0a2ca0dd158f01b833a28c7b46887.1735903029.git.martin.agren@gmail.com>
>
>
> * ps/ci-misc-updates (2025-01-03) 10 commits
> - ci: remove stale code for Azure Pipelines
> - ci: use latest Ubuntu release
> - ci: stop special-casing for Ubuntu 16.04
> - gitlab-ci: add linux32 job testing against i386
> - gitlab-ci: remove the "linux-old" job
> - github: simplify computation of the job's distro
> - github: convert all Linux jobs to be containerized
> - github: adapt containerized jobs to be rootless
> - t7422: fix flaky test caused by buffered stdout
> - t0060: fix EBUSY in MinGW when setting up runtime prefix
>
> CI updates (containerization, dropping stale ones, etc.).
>
> source: <20250103-b4-pks-ci-fixes-v1-0-a9bb95dff833@pks.im>
>
I have sent a patch in the previous day in
<Z26uXy31q83dyxvD@ArchLinux>
However, there is no need to cook this patch because I have decided to
send it with the packed-refs consistency check implementation. I think I
could send the patch in this week.
So, nothing need to be done.
Thanks,
Jialuo
prev parent reply other threads:[~2025-01-04 4:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 21:23 What's cooking in git.git (Jan 2025, #01; Fri, 3) Junio C Hamano
2025-01-04 4:12 ` shejialuo [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z3i1Kgf9M_AiBMBr@ArchLinux \
--to=shejialuo@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.