git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Julian Prein <julian@druckdev.xyz>
Subject: Re: What's cooking in git.git (Jan 2025, #08; Tue, 28)
Date: Fri, 31 Jan 2025 09:51:54 -0800	[thread overview]
Message-ID: <xmqqr04i98hx.fsf@gitster.g> (raw)
In-Reply-To: <xmqqlduulbgn.fsf@gitster.g> (Junio C. Hamano's message of "Tue, 28 Jan 2025 16:18:00 -0800")

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

> * jp/doc-trailer-config (2025-01-24) 1 commit
>  - config.txt: add trailer.* variables
>
>  Documentaiton updates.
>
>  Will merge to 'next'?
>  source: <pull.1871.git.git.1736429142334.gitgitgadget@gmail.com>

I've held the topic (and others that touch documentation) in 'seen'
as we have been seeing GitHub CI breakages on documentation task,
but I think I figured out that it was due to semantic mismerge with
this topic and the recent "everything in Documentation/ now ends
with *.adoc; they are no longer *.txt".  I'll make a merge-fix and
will mark this topic for 'next' when the result proves OK.

Thanks.

      parent reply	other threads:[~2025-01-31 17:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-29  0:18 What's cooking in git.git (Jan 2025, #08; Tue, 28) Junio C Hamano
2025-01-29  7:57 ` Patrick Steinhardt
2025-01-29 14:03   ` Junio C Hamano
2025-01-29 21:34     ` Junio C Hamano
2025-01-30  5:43       ` Patrick Steinhardt
2025-01-31 23:30   ` Jeff King
2025-02-03  6:08     ` Patrick Steinhardt
2025-02-03 21:32       ` Junio C Hamano
2025-01-31 17:51 ` 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

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

  git send-email \
    --in-reply-to=xmqqr04i98hx.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=julian@druckdev.xyz \
    /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).