From: Rob Browning <rlb@defaultvalue.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [PATCH] signature-format.txt: explain and illustrate multi-line headers
Date: Thu, 14 Oct 2021 20:27:22 -0500 [thread overview]
Message-ID: <87v91zgjr9.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <xmqq5ytzcyr6.fsf@gitster.g>
Junio C Hamano <gitster@pobox.com> writes:
> With so little similarity, there is no reason for us to mimick their
> "folding" rule.
Agreed. I'd just lazily guessed it might be 822 (was also thinking of
Debian package headers), but certainly shouldn't have glossed over the
missing colon (for example) -- might be worth making sure the rules
described are covered in the technical docs, if they're not already, and
then perhaps refer to them in the section we're adjusting.
> We limit to the SP and not LWP for another reason. Because the
> exact byte sequence in the object (including the header part of
> "commit" and "tag" objects) determines the name of the object
Ahh, right, of course.
> we would needlessly create many variants of the "same" commit, which
> is not ideal.
Indeed.
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
next prev parent reply other threads:[~2021-10-15 1:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 16:33 [PATCH 1/1] signature-format.txt: add space to fix gpgsig continuation line Rob Browning
2021-10-11 16:41 ` Jeff King
2021-10-11 20:04 ` Junio C Hamano
2021-10-12 2:08 ` Jeff King
2021-10-12 16:54 ` Junio C Hamano
2021-10-13 2:06 ` [PATCH] signature-format.txt: explain and illustrate multi-line headers Junio C Hamano
2021-10-14 5:12 ` Rob Browning
2021-10-14 17:17 ` Junio C Hamano
2021-10-15 1:27 ` Rob Browning [this message]
2021-10-15 15:58 ` Junio C Hamano
2021-10-15 23:29 ` Rob Browning
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=87v91zgjr9.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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.