git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
	Martin Wilck <mwilck@suse.com>,
	Adrian Schroeter <adrian@suse.com>
Subject: Re: [PATCH v2 2/2] read-cache: drop submodule check from add_to_cache()
Date: Sat, 15 Nov 2025 20:06:50 +0000	[thread overview]
Message-ID: <aRjdWunjdMHxpS6Z@fruit.crustytoothpaste.net> (raw)
In-Reply-To: <xmqqseefdq76.fsf@gitster.g>

[-- Attachment #1: Type: text/plain, Size: 750 bytes --]

On 2025-11-15 at 19:57:17, Junio C Hamano wrote:
> A tangent.
> 
> You can (!) place your own sign-off after Peff's, as you would want
> to certify
> 
> c. The contribution was provided directly to me by some other
>    person who certified (a), (b) or (c) and I have not modified
>    it.
> 
> of the DCO, but it seems that it is optional (which I did not know
> about---the explanation in SubmittingPatches stops at "Indeed you
> are encouraged to do so" without making it a requirement).

Yes, I should have done so; my apologies.  Please feel free to add it:

Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>

If you need, I can send a v3 with that fixed.
-- 
brian m. carlson (they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2025-11-15 20:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-12 12:58 git fails to checkout SHA1 submodule in SHA256 repo with --depth=1 Martin Wilck
2025-11-12 16:32 ` Junio C Hamano
2025-11-12 23:37   ` brian m. carlson
2025-11-13 10:15     ` Martin Wilck
2025-11-13 22:51       ` brian m. carlson
2025-11-13 22:57         ` Martin Wilck
2025-11-14 22:55       ` Marc Branchaud
2025-11-15 20:14         ` brian m. carlson
2025-11-12 23:54 ` [PATCH] object-file: disallow adding submodules of different hash algo brian m. carlson
2025-11-13  3:26   ` Jeff King
2025-11-13  3:56     ` Jeff King
2025-11-13 16:29       ` Junio C Hamano
2025-11-14 23:26         ` brian m. carlson
2025-11-15  1:53           ` Jeff King
2025-11-13 23:15     ` brian m. carlson
2025-11-15  0:58   ` [PATCH v2 1/2] " brian m. carlson
2025-11-15  0:58     ` [PATCH v2 2/2] read-cache: drop submodule check from add_to_cache() brian m. carlson
2025-11-15 19:57       ` Junio C Hamano
2025-11-15 20:06         ` brian m. carlson [this message]
2025-11-15 19:53     ` [PATCH v2 1/2] object-file: disallow adding submodules of different hash algo Junio C Hamano
2025-11-17  8:53     ` Martin Wilck

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=aRjdWunjdMHxpS6Z@fruit.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=adrian@suse.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mwilck@suse.com \
    --cc=peff@peff.net \
    /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).