From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Jeff King" <peff@peff.net>, "Patrick Steinhardt" <ps@pks.im>
Cc: git@vger.kernel.org, "Adam Dinwoodie" <adam@dinwoodie.org>,
"Ramsay Jones" <ramsay@ramsayjones.plus.com>,
"Taylor Blau" <me@ttaylorr.com>
Subject: Re: [PATCH] credential-cache: treat ECONNABORTED like ECONNRESET
Date: Fri, 18 Oct 2024 23:27:50 +0200 [thread overview]
Message-ID: <71e8e44e-dbf9-482e-a351-3a82aa1ca5dd@app.fastmail.com> (raw)
In-Reply-To: <20241018052952.GE2408674@coredump.intra.peff.net>
On Fri, Oct 18, 2024, at 07:29, Jeff King wrote:
> [jk: commit message]
>
> Signed-off-by: Jeff King <peff@peff.net>
Just curious. Why this bracket comment (non-trailer line or whatever it
is called) and not a regular trailer? All the bracket comments that
I’ve seen give some comment, often about tweaking the patch or the
commit message. In this case though the whole commit message is written
by one person.
--
Kristoffer Haugsbakk
next prev parent reply other threads:[~2024-10-18 21:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 14:21 [PATCH] builtin/credential-cache--daemon: fix error when "exit"ing on Cygwin Patrick Steinhardt
2024-10-16 14:55 ` Jeff King
2024-10-16 15:09 ` Jeff King
2024-10-16 15:39 ` Ramsay Jones
2024-10-16 20:28 ` Taylor Blau
2024-10-17 2:33 ` Jeff King
2024-10-17 8:46 ` Patrick Steinhardt
2024-10-17 22:58 ` Ramsay Jones
2024-10-18 4:36 ` Patrick Steinhardt
2024-10-17 20:54 ` Taylor Blau
2024-10-16 15:12 ` Ramsay Jones
2024-10-18 4:36 ` [PATCH v2] " Patrick Steinhardt
2024-10-18 5:29 ` [PATCH] credential-cache: treat ECONNABORTED like ECONNRESET Jeff King
2024-10-18 5:32 ` Patrick Steinhardt
2024-10-18 15:33 ` Ramsay Jones
2024-10-18 21:17 ` Taylor Blau
2024-10-18 21:27 ` Kristoffer Haugsbakk [this message]
2024-10-19 21:21 ` Jeff King
2024-10-20 17:08 ` Comment trailers vs. bracketed lines Kristoffer Haugsbakk
2025-05-07 16:41 ` Kristoffer Haugsbakk
2025-05-08 20:24 ` Jeff King
2025-05-07 19:20 ` Junio C Hamano
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=71e8e44e-dbf9-482e-a351-3a82aa1ca5dd@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.com \
--cc=adam@dinwoodie.org \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
--cc=ps@pks.im \
--cc=ramsay@ramsayjones.plus.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).