All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: Patrick Steinhardt <ps@pks.im>,
	 Justin Tobler <jltobler@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH v3 0/2] help: include SHA build options in version info
Date: Mon, 07 Apr 2025 17:33:14 -0700	[thread overview]
Message-ID: <xmqqo6x7ze45.fsf@gitster.g> (raw)
In-Reply-To: <CAP8UFD2a2hA5CEYgr9i5jtw+k8U9gu=Jb01x=W1zekSRBy7B8A@mail.gmail.com> (Christian Couder's message of "Fri, 4 Apr 2025 13:06:33 +0200")

Christian Couder <christian.couder@gmail.com> writes:

> On Fri, Apr 4, 2025 at 11:20 AM Patrick Steinhardt <ps@pks.im> wrote:
>>
>> On Thu, Apr 03, 2025 at 09:05:27AM -0500, Justin Tobler wrote:
>> >
>> Thanks, I'm happy with this version.
>
> I am fine with it as well. Thanks.

Thanks, all.  Will replace.  Let me mark the topic for 'next'.

      reply	other threads:[~2025-04-08  0:33 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28 17:01 [PATCH 0/2] help: include SHA build options in version info Justin Tobler
2025-03-28 17:01 ` [PATCH 1/2] help: include SHA implementation " Justin Tobler
2025-03-29 11:36   ` Junio C Hamano
2025-03-31  7:19     ` Patrick Steinhardt
2025-03-31 17:46       ` Justin Tobler
2025-04-01  9:47       ` Junio C Hamano
2025-03-31 17:21     ` Justin Tobler
2025-03-28 17:01 ` [PATCH 2/2] help: include unsafe SHA-1 build info in version Justin Tobler
2025-03-29  8:42   ` Christian Couder
2025-03-29  8:58 ` [PATCH 0/2] help: include SHA build options in version info Christian Couder
2025-03-31 18:17   ` Justin Tobler
2025-04-01 20:36 ` [PATCH v2 " Justin Tobler
2025-04-01 20:36   ` [PATCH v2 1/2] help: include SHA implementation " Justin Tobler
2025-04-02  7:38     ` Patrick Steinhardt
2025-04-02 11:26       ` Christian Couder
2025-04-02 11:27         ` Christian Couder
2025-04-02 14:56         ` Justin Tobler
2025-04-01 20:36   ` [PATCH v2 2/2] help: include unsafe SHA-1 build info in version Justin Tobler
2025-04-02  7:38     ` Patrick Steinhardt
2025-04-02 15:59       ` Justin Tobler
2025-04-03  5:10         ` Patrick Steinhardt
2025-04-03 14:05   ` [PATCH v3 0/2] help: include SHA build options in version info Justin Tobler
2025-04-03 14:05     ` [PATCH v3 1/2] help: include SHA implementation " Justin Tobler
2025-04-03 14:05     ` [PATCH v3 2/2] help: include unsafe SHA-1 build info in version Justin Tobler
2025-04-04  9:20     ` [PATCH v3 0/2] help: include SHA build options in version info Patrick Steinhardt
2025-04-04 11:06       ` Christian Couder
2025-04-08  0:33         ` 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=xmqqo6x7ze45.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jltobler@gmail.com \
    --cc=ps@pks.im \
    /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.