From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
Cc: git@vger.kernel.org
Subject: Re: kh/trailers-no-urls
Date: Thu, 13 Aug 2026 11:33:45 -0700 [thread overview]
Message-ID: <xmqqbjb5swdy.fsf@gitster.g> (raw)
In-Reply-To: <6e990986-2d7e-492f-aa40-d26cca4f58f4@app.fastmail.com> (Kristoffer Haugsbakk's message of "Thu, 13 Aug 2026 19:35:18 +0200")
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
> On Thu, Aug 13, 2026, at 06:45, Junio C Hamano wrote:
>> * kh/trailers-no-urls (2026-08-02) 2 commits
>> - trailers: stop recognizing URLs as trailers
>> - Merge branch 'kh/doc-trailers' into kh/trailers-no-urls
>> (this branch uses kh/doc-trailers.)
>>
>> The trailers code has been taught to avoid mistaking a line that has
>> '<token>://' at the beginning as a trailer line.
>>
>> On hold, waiting for the base topic.
>> cf. <20260803152025.GA189075@coredump.intra.peff.net>
>> cf. <xmqqmrv42lrg.fsf@gitster.g>
>> cf. <xmqqtspbz00x.fsf@gitster.g>
>> source: <URLs_not_trailers.b13@msgid.xyz>
>
> The status of the topic kh/doc-trailers is “Will merge to 'next'”. I
> will wait until that topic is in `master` and send out a new version of
> this topic then. Thanks.
Once we are reasonably sure that the base topic would not go away or
change drastically, it is fine to depend on it before it is merged
to 'master', if you choose to. kh/doc-trailers is sitting at the
tip of 'next' as of this writing, FYI.
Thanks.
next prev parent reply other threads:[~2026-08-13 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 4:45 What's cooking in git.git (Aug 2026, #05) Junio C Hamano
2026-08-13 7:59 ` Patrick Steinhardt
2026-08-13 17:36 ` Junio C Hamano
2026-08-13 17:35 ` kh/trailers-no-urls Kristoffer Haugsbakk
2026-08-13 18:33 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-03 19:09 What's cooking in git.git (Aug 2026, #01) Junio C Hamano
2026-08-04 19:16 ` kh/trailers-no-urls Kristoffer Haugsbakk
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=xmqqbjb5swdy.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.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.